On Wed, Nov 12, 2003 at 01:29:15PM +0100, Kaare Rasmussen wrote: > Hi again > > > I've seen soap mentioned with Poe as well. > > I tried POE::Component::Server::SOAP and I'm amazed as how simple it was ti > install and start the test. > > So I've decided to dig deeper. I hope someone will have the time to answer a > couple of questions.
Unfortunately it uses SOAP::Parser. This module seems to have issues with anything but trivial SOAP requests. It seems to be extensible through experimental, undocumented means. Unfortunotaly, the parser that comes with SOAP::Lite seems heavily intertwined with the SOAP suite of modules. I've spent most of the day unsuccessfully trying to use it by itself. I'd greatly appreciate someone with a guts-level knowledge of either of these modules to provide a sample SOAP parser I can incorporate into Server::SOAP. > > - The soapserver will talk to a PostgreSQL database. > > Will POE::Component::Server::SOAP be able to handle several requests > concurrently ? Yes. PoCo::Server::SOAP detaches from Server::HTTP and can process requests asynchronously. Combined with an asynchronous DBI agent (and there seem to be ever-growing numbers of them), you can concurrently offload multiple requests to one or more SQL servers. > Looking at http://poe.perl.org, I see a discussion about asynchroneous > database access. Will I have to use POE::Component::DBIAgent to be sure that > the server will respond even when there's a large database request in action? > DBIAgent seems to be using DBI directly. I'm using DBIx::Recordset, so I guess > I would have a problem here. > > > - Can a Poe-server hold the state over several requests ? > > Any examples of using tickets or cookies ? It's a common pattern, but it's not one that has been generically solved yet. I don't recall which (if any) Cookbook recipe covers it. -- Rocco Caputo - [EMAIL PROTECTED] - http://poe.perl.org/
