Tina, in thinking about the Winsock conversation, if I recall, it's like two devices communicating with each other. If you don't communicate as fast as it thinks you should, because it is busy, it will give you an error. It's pretty strange. What is your time-out set for? If it is 0, you may want to change that a little bit. For those of you who got this message, please ignore the remainder of my message. There was a very good explanation for this, so here it is. Winsock, or Windows Sockets, is the component responsible for socket-based communications, primarily network sockets. Network sockets can be thought of as virtual sockets that sit at either end of a communication channel, a virtual wire. When you want to talk to a computer on the internet, you open a socket and establish a connection. When the remote system agrees to talk to you, you will get a code indicating that, and your program can just send and receive stuff over that socket, in this case electronic mail transaction commands over a TCP session for reliable communication using POP3. Now, you and your friend the POP3 server are chatting away, but at some step along the dialog in which you take it in turns to talk to each other in a polite fashion, you are kept busy by something not related to the network; perhaps you are filing away the mail you have just received, and the disk activity is holding you up. Your friend is regrettably rather busy and has many more people hungry for attention, so he has decided that if you should not say something for a certain amount of time, called a timeout, he will regrettably have to just shut his socket on you. You are very busy for some time, and exactly this happens; he disconnects his socket from the transaction. When you come back from business and next say, "Ok, give me message number 31, please", your return value from the Winsock library is not a success code but an error to the effect that the transaction did not occur. This error has a constant number, and it is this number that you are reading in your Win! sock! error messages. The solution is twofold: 1. This is usually not under your control, but arrange for the BrailleNote to hurry up its operations. You could start by compacting your database, flushing away messages you don't need, and the like. 2. Increase the timeout before disconnection at the POP3 server. If you're greater-than ever in control of the POP3 service (and I'm guessing you are not), give this poor BrailleNote time to stutter out of its business and resume the dialog with the POP3 service by preventing the server from shutting the connection on the BrailleNote. Try asking your ISP what the timeout is, and/or whether or not it may be increased. This change usually has a noticeable effect on server performance, so ask nicely.
>----- Original Message ----- >From: tina <[EMAIL PROTECTED] >To: Braillenote List <[email protected] >Date: Fri, 15 Oct 2004 20:07:12 -0700 >Subject: RE: [Braillenote] how do you use keyword? >Hi. >I've gotten a lbot of winsock 10057 errors lately and am wondering if it >happens when the database is corrupted as well as when you have very little >memory because it happened to me tonight and I got rid of it so am writing >this message again just in case it got rid of the first one. Is this possible >though because it's happened to me a lot lately >and normally does not unless I'm dealing with maybe #ydjj messages at a time >and that's not usually the case >___ >To leave the BrailleNote list, send a blank message to >[EMAIL PROTECTED] >To view the list archives or change your preferences, visit >http://list.pulsedata.com/mailman/listinfo/braillenote
