We can check for slashes / and \ in the path, not just first character.
This will work both on Unix and Windows.
Zoran Vasiljevic wrote:
Am 10.06.2005 um 17:09 schrieb Vlad Seryakov:
As for Unix sockets, on windows path will be different, on unix
different but functionality will be there.
Yes but the decision on wether the address is for a TCP or unix-domain
socket is based on parsing the address string, right?
So, on Unix, the unix-domain socket (AF_UNIX) would be
something like:
/path/to/file
whereas on Windos it will/might be
C:\path\to\file
The parsing will just never discover that the above
is the unix-domain socket and will go to parse the
IP address instead (and fail). This is what I ment.
Zoran
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you
shotput
a projector? How fast can you ride your desk chair down the office luge
track?
If you want to score the big prize, get to know the little guy. Play to
win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
--
Vlad Seryakov
571 262-8608 office
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
