| Reply | « Previous Thread | Next Thread » |
|
We are seeing some strange behaviour when using SSL socket connections from various Nokia phones.
It is almost as if any call to the sockets InputStream read() method will return bytes, regardless of if there are any bytes in the receive buffer. The byte data returned is random data. The same code works fine when on an unsecure socket. Is this known behaviour at all? |
|
I should add to this it may not be actually returning bytes, but the length returned by read() suggests it is.
We would normally block in the read() waiting for the next message, but instead it always returns. The simulators don't seem to show the same behaviour. Any help out there? |
| Reply | « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|---|---|
| Thread | Thread Starter | Forum | Replies | Last Post |
|---|---|---|---|---|
| Secure Socket read gets stuck in a loop on N70 device | jestyjames | Symbian Networking & Messaging | 5 | 2007-01-08 11:02 |
| Clarifications on User Data, User Data Binary and User Data Header | saijee | General Messaging | 2 | 2004-09-15 23:47 |
| Bluetooth L2CAP Socket: Read() vs. Recv() | jamespinakis | General Symbian C++ | 2 | 2004-06-11 01:44 |
| how to add HTTP header to data sent using socket? | smallfish_ntu | Symbian Networking & Messaging | 3 | 2003-09-10 17:35 |
| Bluetooth L2CAP Socket: Read() vs. Recv() | jamespinakis | Bluetooth Technology | 1 | 2003-06-10 23:52 |