> To me it sounds that you expect the clients to be fairly 'heavy', in which > case the Merlin overhead could be considered fairly low, in terms of startup > time and memory requirement.
you are right. i'll try to let merlin run embedded in an eclipse plugin at client-side. in fact i already succeeded to port the "generic embedding" example to a plugin. the resulting DefaultKernel is obviously running and can be shut down programatically. but i have no clue how to make my block boot. could you give me one more hint? > > > this framework is also extensible with user defined > > protocols (if i could use avalon services for that?). > > Sounds like a plan. Service-oriented architecture is the way to go. Merlin > excels at it, but Eclipse itself ain't too bad either with their Plugin > Connections (or what is proper term?). > Going with Eclipse plugins for extending your framework, you will end up with > a bigger difference between server and client code. > Going with an embedded Merlin adds weight to your subsystem, but I still tend > to recommend this, since you probably down the line will have more types of > clients, than Eclipse based ones, such as webservers and perhaps the CDO > servers being each others clients. the more i think about it the more i like the idea to combine both merlin and eclipse at client-side as well as at server-side (but eclipse in headless-mode to avoid the ui). this way the merlin (avalon?) components could benefit from eclipse's plugin registry and its web update manager. /eike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
