It sounds like you're putting the cart before the horse. POE::Wheel::Run includes parent/child process communication. POE::Component::Client::HTTP is not a a HTTP server. If your "clients" are simple programs, they could be implemented with plain LWP to talk to a POE-based HTTP server. You haven't explicitly said the httpd is running POE; I'm assuming yes because of the POE::Wheel::Run.

What I think (which is based on incomplete information and is probably wrong):

• Plain old clients. LPW, curl, wget, whatever. This handles the client/httpd communication.
• HTTP server, using one of the POE httpd components (your choice).
• POE::Wheel::Run to run child processes and deal with httpd/child communication.
• Worker pool management is a vague concept and probably includes some custom logic. Until I know more, you probably write this part.

I would have the child processes report their status as it changes, and then store that status in the HTTP session (not a POE session). When the client polls for status, it can be satisfied by the session information rather than asking the child process (which may have exited or crashed anyway).

http://poe.perl.org/?POE_Cookbook/Job_Server is a telnet based job server. It's not appropriate for your task, but it does show one way to write a server that accepts jobs and then runs them in separate processes.

Sorry for the vague answer. I may be able to narrow down my advice if you provide more specifics.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.