--- GUIRY Aroun <[EMAIL PROTECTED]> wrote:
> Hi all > > I am doing a simple ssl server/client. I use a > select function to read > and write in the socket. > From my client I send 1KB of data, in one time, and > then I expect to > read it in the server. > In the server appli, I have got a select read hit, > and I read 500B. > Then I expect to have a second select read hit to > finish the read. But > it never happened, and the program is blocked in the > select. > > If I send a new packet from the client I can read > the missing packets, > but not the new one. > I use non-blocking sockets. > The read condition signaled by select() call should be cleared before you call it again. Also TCP doesnt have any message boundaries. So I think you cannot hope to get two notifications for one receive. The reason you get it when you send another packet is the notification you get for the "another packet", not for the previous remnant. Obviously when reading you have to read the remant first. In other words it is not possible to do what you plan to achieve. In fact it is not even guaranteed in TCP that you will get all the packet in one read itself. regards, Girish > > Can you help me. > > Thanks > Arun > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet > Messaging Program. > > ______________________________________________________________________ > OpenSSL Project > http://www.openssl.org > User Support Mailing List > openssl-users@openssl.org > Automated List Manager > [EMAIL PROTECTED] > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]