Hello,
I'm experiencing some odd behavior and was wondering if anyone else
is seeing the same thing. I have a project that uses REAL's built-in
POP3Socket to send the "UIDL" command via SendServerCommand and
processes the response using the ServerCommandReply event. I've found
that moving the project from REALBasic 2006r1 to REALBasic 2006r2
introduces a new problem.
In 2006r2, if the server's response arrives in more than one TCP
packet, ServerCommandReply is correctly called again when the second
packet arrives, but with an empty Command parameter. So you'll get
one event where the Command parameter is "UIDL" and a second where
Command is an empty string. This was not the case in 2006r1.
This would be just fine by me if it didn't intermittently prevent the
socket's own built-in methods from working properly. After the UID
list is received, I call RetrieveMessage. The socket dutifully sends
out the "RETR" command and receives the server response but rather
than triggering the MessageReceived event, it calls
ServerCommandReply, with an empty Command parameter.
Anyone else having similar problems with the ServerCommandReply event?
Thanks,
Navdeep Bains
Bains Software
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
