You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The socket abstraction layer should not introduce any dependencies which are not critical to implementing a socket API. Currently, mbed-net-socket-abstract has a target dependency on mbed-mesh-api, which introduces this tree:
@bremoran , yesterday I published mbed-mesh-api v0.0.3 that contains dependencies to mbed-core and mbed-6lowpan-adaptor. Please check if the new version is better.
Another option would be to remove mbed-mesh-api dependency from mbed-net-socket-abstract and let applications have dependency to mbed-mesh-api directly. At the moment application need to use the mbed-mesh-api for connecting to mesh network.
Since the mbed-mesh-api is not strictly necessary for implementing the socket API, I think it should be removed from the dependency tree of mbed-net-socket-abstract. Likewise, I think it would be a good idea to remove mbed-net-lwip-eth from the dependency tree of mbed-net-lwip. I think it belongs somewhere else, possibly under mbed-net-interface (as yet uncreated), or similar.
The socket abstraction layer should not introduce any dependencies which are not critical to implementing a socket API. Currently,
mbed-net-socket-abstract
has a target dependency onmbed-mesh-api
, which introduces this tree:The socket abstraction layer should not require coap, mbed-client, ecc support, libx509, etc.
Maybe mbed-6lowpan-adaptor would be a better target dependency for mbed-net-socket-abstract.
The text was updated successfully, but these errors were encountered: