Re: [MacPerl] Unix socket incompatibility?

[schinder@pjstoaster.pg.md.us (Paul Schinder)]

shaw@ISI.EDU writes:
[snip]
} 
} 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.

What kinds of end-of-lines are you sending down the wire?  Remember
that network protocols usually want \015\012 (or in some cases in http
\012\012, as I recall), and if you write that \r\n or \n\n in MacPerl
you're sending exactly the wrong thing down the line.  I've learned
 from experience that a lot of different types of servers won't respond
at all if you send incorrectly terminated lines.

} 
} Erin
} 
---
--------
Paul J. Schinder
NASA Goddard Space Flight Center,
Code 693, Greenbelt, MD 20771 USA
schinder@pjstoaster.pg.md.us