Re: Re: Socket response inconsistent

The sending of the UDP message has been consistently ok, if I print the return of send that's consistent and fine.

The point of the script is to test the status of the server at the other end, when it receives a UDP message goes off and does stuff and returns a UDP response.

I dont want to go ahead and check recv unless the IO::Select has a consistent and checkable response, but even if i turn $read into a proper array, it doesn't help much.

Points taken on your box does it, I'll check versions, and have been looking out for a TCP/IP book for a while, time to bite the bullet, cheers :)

Comment on Re: Re: Socket response inconsistent

Replies are listed 'Best First'.
Re: Re: Re: Socket response inconsistent by Cubes (Pilgrim) on Jul 31, 2001 at 19:45 UTC
When I did a recv after getting something back from select, I consistently got empty (i.e. zero byte) responses. Though I'm not entirely sure what is supposed to happen here, this does make some kind of sense to me -- select is saying "yeah, the socket's there, go ahead and read from it," even though there is no data presently waiting. As for books, I highly recommend UNIX Network Programming by W. Richard Stevens, and Douglas Comer's Internetworking with TCP/IP (Vol. I covers the basic, low-level stuff). Not exactly light bedtime reading, but they will give you a solid understanding of what lies beneath all these slick perl modules.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Socket response inconsistent
by Cubes (Pilgrim) on Jul 31, 2001 at 19:45 UTC

As for books, I highly recommend UNIX Network Programming by W. Richard Stevens, and Douglas Comer's Internetworking with TCP/IP (Vol. I covers the basic, low-level stuff). Not exactly light bedtime reading, but they will give you a solid understanding of what lies beneath all these slick perl modules.

[reply]