Hello exilepanda,

If you do it the way I described, the %ENV variables are already set-up for you. Do not touch the %ENV, but copy the %ENV to a temp hash. And remember you still need the GET / POST data ( the actual $Todo work ) from the WebServer. ( Example ).

    my $Todo = ...;    # Data sent via GET or POST from browser via We
+bServer    
    my $environment = '';
    foreach my $env ( keys %ENV )
    {   $environment .= "$env\t$ENV{$env}\n"; }

    my $send = pack("N",length($environment) ) . $environment .  pack(
+"N",length($Todo) ) . $Todo;
    my $ret = send_data( $svr, \$send );   # Send to processing Perl s
+cript
[download]

Now the second client has the environment of the WebSever, and it's own %ENV from Perl. The processing client uses %TempENV for WebServer info and it's own %ENV if it needs it.

It's clean and you don't have to get into the error handling of the WebServer.

Good Luck!

Regards...Ed

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.