[MNEDC] Refactoring in terms of Architecture about edge-home-orchestration-go HOT 8 OPEN

@t25kim @MoonkiHong : We checked this modification. Seem to involve cyclical importing which Go doesn't support. So we are checking on changing the same and testing.

from edge-home-orchestration-go.

@t25kim @MoonkiHong : We checked this modification. Seem to involve cyclical importing which Go doesn't support. So we are checking on changing the same and testing.

@suresh-lc Thank you for your prompt analysis. As you suggested, let us discuss further about the best approach once you completed the check-up on changing the same and testing stuff, especially about the cyclical importing which GoLang does not support. We will wait for your updates. ^^

from edge-home-orchestration-go.

This issue is still valid since the latest merged PR #178 resolved Change package name from mnedcmgr to mnedc or something..

from edge-home-orchestration-go.

@ayush-kr @suresh-lc What about your opinion (from the contributors' perspective)?

from edge-home-orchestration-go.

I think that the mnedcmgr function should be under the discoverymgr since they are similar with respect to functionality.
How about moving the mnedcmgr code under the discoverymgr?
Below should be changed.

• Change package name from mnedcmgr to mnedc or something.
• The discoverymgr should call StartMNEDCServer() and StartMNEDCClient().

Any comments are welcome!

@t25kim Thank you for a great suggestion. We will estimate its feasibility to migrate the functions of the mnedcmgr into discoverymgr with regarding contributors of mnedc.

from edge-home-orchestration-go.

All the implementations have been done

from edge-home-orchestration-go.

Sorry. But this has not been resolved yet.

from edge-home-orchestration-go.

Sorry. But this has not been resolved yet.

Ok i get you, lets check this how to go about.

from edge-home-orchestration-go.