On Wed, Jul 16, 2003 at 11:00:31AM -0500, James.FitzGibbon wrote:
> Greetings all.
> 
> I'm writing a POE server using POE::Component::Server::SOAP (which in turn uses
> POE::Component::Server::HTTP).   The problem is I want to bind the server to
> a single address, and as far as I can tell, this is not directly supported.
> P::C::S::TCP supports an 'Address' parm, but ::SOAP and ::HTTP don't allow for
> this to be passed through to the ::TCP constructor.
> 
> Would patches to address this be useful to other people?  I'm also going to try
> to address whatever causes this error to be emitted when ::HTTP is used:
> 
> The _signal event is deprecated.  Please use sig() to register a signal handler at 
> foo.pl line 5

Arthur Bergman's the author of Server::HTTP.  He's taken on two very
large responsibilities in the past couple weeks: Incorporating threads
in POE, and leading development of PONIE (the perl 5 on parrot project).
I don't know if he has time left to work on Server::HTTP, but I hope he
has time to apply patches.

Server::SOAP is mine, and I'll be happy to apply patches, sure.

> I'm tempted to use Class::Container in doing this, but I'm not sure if that would
> make the components 'tainted' in some way.  If you read the description of that
> module, the situation it describes is a perfect match for what is going on in
> ::TCP -> ::HTTP -> ::SOAP:

[...]

> Of course, to do it properly would require changes in two CPAN modules and in a
> core POE module, plus changes to probably a few other components that I'm not
> using but which also use ::TCP.
> 
> So maybe that part is aiming a bit high at first, but the 'Address' part is doable
> without blowing too much up.  8-)

Class::Container looks very interesting.  If someone could put together
a syntactically correct but non-functional prototype/mock-up for this,
it would be a great help.  Meanwhile, I'll put Class::Container on my
to-try list, but this may take a while.

My last attempt at a grand unified object model for POE was container
based, but it had issues that I found to be disappointing.  I've written
a report on poe.perl.org about why I think it failed.

Dieter and Helen (and others) looked it over at YAPC::NA, and they have
some ideas for making it work.  I hope to see their response to my
post-mortem report.  Maybe Class::Container can help here.

-- Rocco Caputo - [EMAIL PROTECTED] - http://poe.perl.org/

Reply via email to