On Tue, 1 Jan 2002, Manuel Lemos wrote:
> > The project we are currently doing, SRM, works a lot like the things
> > you are describing, the only real difference is that we don't use SOAP as
> > transport protocol, but a bytestream protocol. However, adding a XPL-RPC
> > (or SOAP) layer is on the TODO list to. In the next few weeks, I'm going
> > to setup upp some demos, and release some of the code (the PHP extension)
> > so that other can play with it too a little.
>
> I don't think what I suggested is anyway related. What I suggested is
> way built-in PHP to consume remote Web services provided via SOAP. What
> you have is session data manager working in a controlled client-server
> architechture. The service you provide is very specific. Web services
> are defined by remote providers.
I think I know quite good what SRM can do, and that is not only session
data. Besides storing session data, which is not the main goal of SRM
anymore, it can do things like persistent objects (whose methods can be
called remotely), self contained scripts acting on events, function
libraries (written in PHP, accessed through the deamon from a client side
script).
>
> If you already have a bytestream protocol for exchanging session data
> between the client and the server, I doubt that a XML-RPC or a SOAP
> transport layer would provide any advantage. It would make data
> marshalling and exchaging slower without providing any extra flexibility
> (I think).
It would certainly be slower, but it also extends SRM's capability to work
a lot easier with other languages than PHP. The only thing that need to be
written to support a new language is the clientside in that case.
Derick
---------------------------------------------------------------------
PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED]
SRM: Site Resource Manager - www.vl-srm.net
---------------------------------------------------------------------
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
