[openbeosnetteam] Re: Wrapper library

Hello,

>       [Zenja Solaja]  I've looked at the links you've provided, a very
>informative read.  Eric has taken the approach of replacing one component at
>a time while always having a complete module (the other untouched
>components) until eventually all components are replaced.  This ensures
>compatibility and functionality where this approach is possible, and for
>some kits (ie. the Support Kit) this is the way to go since each component
>is separate from the others, hence you can replace them peice-meal (ie.
>BString and BList).
>
>       Unfortunately, with some kits (like the media kit and the
>net_server) we've got the problem of dependency with unknown internal
>functions and an unknown state machine which constitutes the server.  We
>know the public interface, but not what states and messages it sends to the
>server.  Erics approach can help with some components which are
>non-dependant on the server internals, but the brunt of the server needs a
>complete replacement, hence the global pluggin support suggested by Marcus
>seems like a more appropriate path for us to take.

Good and valid point, granted :^)
So now we all rely on you for building the empty cpp files... ;-)

Jean

Other related posts: