I have developed a lightweight Stateless Web Service which will connect
to a Stateful server which manages database connections.
I would like some ideas on how to build the Stateful server.
A typical session would go something like this (from the clients point
of view):
What I want is some info on how the lightweight Web Service should talk to the Statefil server.
I'd go for standard http, and hope I'm not giving away too much here ;)
but, creating the server as a cgi web-server app has some big up-front advantages :
- common protocols (don't need to learn different kinds) - cgi is slower *but* more robust : if anything goes wrong it just dies. You propagate the error back to the client and they retry. Saves having to monitor and restart the server for *any* reason. - no memory leaks possible - midas is either hard to or can't run as a service (can't remember which) - simple dev. model - simple installation / management - upgrade path to securing (via ssl) - very reconfigurable - you can keep chain as many servers as you want (ie load balancing etc). - good tools available (log analysers and such) - good components available (ics / indy)
OTOH : - cgi is slow - delphi/web may be slower than Apache/php or IIS/asp (YMMV) (although you can switch to them transparently from the clients perspective) - haven't tried soap. - custom middleware is a lot of fun (just, please, not CORBA...)
CGI is a very easy starting point, and rocks until speed starts to matter (basically after: load, reliablity, hardware).
Cheers, Kurt.
_______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
