Re: [MacPerl] Unix socket incompatibility?

[Erin Shaw <shaw@isi.edu>]

Unix->Mac differences found during the port of our CGI client:

1) The pathnames, of course.

2) The URL: SCRIPT_NAME and PATH_INFO must be delimited by a $ on a
   Mac, where as in Unix, we had (rightly or wrongly) used a /.
   
3) Can't use exec(): we still don't have a workaround for this, but 
   are looking at Applescript.  Perl waits around for our launched
   application to exit, which keeps the stream to Netscape open.

4) Client code socket problems.

   The code comes right out of "Programming Perl", p. 344, with the
   exception that you can't fork() for the response (OK for us, but
   could be severely limiting).  The macperl client can make a
   connection, but the [NCSA Web] server never sees or responds to it.

   a) Our client *can* connect to a dummy server on a different port.
   b) It's not the HTTP header that's being sent, unless it's being
      mangled.
   c) I am not able to test this code stand alone: when I run it in
      the macperl script environment, it hangs and there appears to be
      no way to abort, expect to quit the whole environment.

Looks like we're stuck on this for a while.  Any help would be
appreciated, especially helpful would be a piece of tried and true
Macperl socket code.  Thanks.

Erin

>Hey, did you have to modify the code much for the port?
>Other than the usual path delimeter stuff?  A pointer to the
>portedcode or a summary of what you had to do whould be
>hehelpful; i'll have to just re-write the same thing again.
>It would be lovely to have some code available or a
>nice list of needed changes...  I'll be glad to help you
>try to debug if you post.

>kevin
>lenzo@cs.cmu.edu

>> I'm having difficulty using standard Unix TCP socket/bind/connect code
>> (ported to MacPerl) to connect to our Unix web server.  The code works
>> successfully in Unix, and appears to work on the Mac (the error codes
>> are clean), but the web server either ignores, or never gets the
>> connection because it doesn't appear in it's log file and no response
>> is returned to our client.
>>
>> Erin