- From: Micheál Healy <michael.healy@engitech.ie>
- Date: Wed, 28 Mar 2001 17:48:51 +0100
- To: <xml-dist-app@w3.org>
Hi, We've got a new project and the chance of designing a new three tier architecture from scratch (usual presentation server forwarding requests to an application server which implements all business logic and connects to the database server). We decided to use XML to encapsulate the communication between presentation and application. It makes sense for its flexible object serialization. At a higher level we are then considering the use of SOAP or XML-RPC, but we need to implement the concept of a session, with single login and secure communications, and an RPC over HTTP doesn't seem to offer that capability. We might resort to EJBs transmitting SOAP messages as strings if we find an economical way to implement a SOAP server that accepts strings as well as socket streams, but it seems like the architecture might turn out to be more complex than necessary. Are we missing some obvious feature on SOAP that would make the EJBs unnecessary? Any comment would be appreciated, TIA, Micheál Healy
Received on Wednesday, 28 March 2001 11:49:19 UTC