> -----Original Message----- > From: Milind Tendulkar [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 25, 2003 5:58 PM > To: Avalon framework users > Subject: RE: Cornerstone examples for phjoenix missing? > > Thnaks. But just to begin with, should a server app be exposed over a port > using cornerstone apis or through configuration files? and how client > would communicate to server? I browsed through cornerstone javadocs to see > ServerSocket class. >
Not sure if I'm following your question, but here's some thoughts: The idea of the 'exporter' extension for Merlin was that you wouldn't have to do _any_ extra coding to get AltRMI/JNDI exporting of a service. All you would have to do is add the appropriate meta-data or configuration information and 'magically' (since we like that word around here lately) your service would be available for external apps to lookup via JNDI or AltRMI. This works well for "remoting services" or applications where you might otherwise use EJBs. If you need more control over the actual socket and perhaps need to use or develop a custom socket protocol, then you can use the Cornerstone block to provide you with the sockets. At that point you're working on a much lower networking level and will involve explicit programming and handling of the sockets in your application. So which approach you use depends on your needs. Hope that makes things a little more clear. J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
