I've got a weird problem with my HTTPSocket. First of all, this all worked just fine before I changed things, but now, it seems like the DownloadComplete event isn't firing. The application just sits there hogging processor time, not writing to the hard drive, not using any extra memory, just spinning the wheels. Whenever I inspect the code execution, it seems clear and simple that the DownloadComplete event simply isn't firing when the file is done. The socket remains connected, too.
Okay, more information...
The download does complete successfully. The file is where it is supposed to be. It's complete and not corrupt. The binary stream is still open, so quitting the debug application releases the file, and it's perfectly usable. I'm using HTTPSocket.Get(Address) to store the file to the hard drive, and I'm using a thread to monitor progress. When the download has completed, the ReceiveProgress event fires once more; there is no new data, and bytesReceived equals totalBytes. Nonetheless, DownloadComplete does not fire. The socket remains connected and the binary stream remains open.
And, the question still stands... Is there something simple that causes the DownloadComplete event to not fire?
Thanks, Andrew Keller _______________________________________________ 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>
