hi there, i'm currently investigating how to provide a better infra structure to an existing client-server-application. this way i came to merlin (an alternative for me could be a plugin collection in a headless eclipse environment, but i'd prefer the merlin approach since it seems suited better for the server scenario).
my existing app shares transport/signalling code between server and client. at that abstraction level there is no difference between client and server role. in other words: the server is only passive in that it never connects to a client, but once a client has connected, the server may also send asynchronous requests to the client. each peer of the connection has a socket and two threads (transmitter and receiver) with rather complex protocol logic. i don't want to have the client start a merlin container but it would be nice for the server to benefit from the merlin architecture (config, logging, jmx, ...) could anyone suggest how to componentize my code on the one hand and to deploy parts of it to a client without merlin on the other?! /eike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
