There is a POE::Component::Server::SOAP component for POE already, but I wasn't able to get it working. I suspect Rocco made it as a proof of concept, but he will know better than I do.
It is possible to just use POE::Component::Server::HTTP and send off the request data to, IIRC, SOAP::Transport::HTTP::Server. I did this successfully last week, but don't have the code in front of me right now. I'll have more info later. Peter Guzis Web Administrator, Sr. ENCAD, Inc. - A Kodak Company email: [EMAIL PROTECTED] www.encad.com -----Original Message----- From: Kaare Rasmussen [mailto:[EMAIL PROTECTED] Sent: Monday, November 03, 2003 6:36 AM To: [EMAIL PROTECTED] Subject: soap server Hi Having lurked on this list (when time permits) for a while, I'm still not sure for what range of applications Poe should be the right choice. Right now I'm looking at writing a soap server as a backend to an embperl application. SOAP::Lite includes an example for using HTTP::Daemon, which looks simple. I've seen soap mentioned with Poe as well. Why would I want to use Poe over HTTP::Daemon and vice-verse ? If I add this information - The soapserver will talk to a PostgreSQL database. - I'm not sure how to handle the database connection. No need for a new handle for each new request, but handles expire after some time of inactivity. - I'd like the server to do its own maintenance. Once in a while it could remove old sessions or do other tricks like time-based business methods. - It will perform a lot of methods from a lot of business modules. - Can a Poe-server hold the state over several requests ? I guess the answer is yes, but do examples exist ? - How about security. I suppose that ssl is no problem ? - Authenticity - the server has to know who's requesting the service and see if they'r allowed to do so. -- Kaare Rasmussen --Linux, spil,-- Tlf: 3816 2582 Kaki Data tshirts, merchandize Fax: 3816 2501 Howitzvej 75 �ben 12.00-18.00 Email: [EMAIL PROTECTED] 2000 Frederiksberg L�rdag 12.00-16.00 Web: www.suse.dk
