Anatole, thank you for you message. JNDI is really about the hot-deployment you speak of. It's a publishing mechanism for an application to make itself available to others. It a mechanism for one application to obtain a "handle" to all of the functions provided by another self-published application. It's dynamic.
XML is just a file on the file system. It might be human readable, but it's not that easy to author correctly without (another) tool. You mentioned of control over serial requests. Are you referring to the asynchronous nature of remote calls? The nice thing about designing software to work in an asynchronous mode is that it becomes prepared to receive a "message" at any point in the chain of events - not just at the entry point, or beginning of the process. It opens up several new possibilities. Like you, we'd like to see the flexibility of Flash Remoting remain if we are to adopt Flex. The additional functionality of FDS solves several problems. However, achieving a high level of integration with our business logic is the primary job of the gateway. If the gateway makes it harder to integrate with our server side applications the benefits are offset. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
