realbasic-nug
[Top] [All Lists]

Re: Socket Taking Over. Need a Thread?

To: realbasic-nug at lists dot realsoftware dot com
Subject: Re: Socket Taking Over. Need a Thread?
From: "Theodore H. Smith" <delete at elfdata dot com>
Date: Sun, 30 Dec 2007 13:14:18 +0000
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <mailman dot 11875 dot 1198980231 dot 259 dot realbasic-nug at lists dot realsoftware dot com>
> To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
> Message-ID: <33A8632C-4B8C-44BD-8DBB-2890C1CE61AA at jettfuel dot net>
>
> I am working on an HTTP server that will be incorporated into several
> projects.  In testing, I have an HTML page with a form that allows
> upload of a file.  Everything is working fine, but the application
> becomes unresponsive when uploading a file of any size.  I have in
> the DataAvailable event code that reads what's in the socket buffer
> and adding it to an string that is acting as a buffer.  Is there a
> better way to implement things so that the application remains
> responsive and other connections can continue to operate?  Should I
> try using a Thread to handle reading the data and remove the code
> from the DataAvailable event?

Set .YieldsToThreads to true.

Or maybe it's called .YieldsToSomethingElse

Or .YieldsWhatever

I dunno what it's called. But I think it starts with .Yields :)

Anyhow, that's exactly what you are looking for. My sockets don't  
leave my apps unresponsive. I even have progress bars in the app which  
let the user know how it's going while he goes off and does other  
things in the app.

--
http://elfdata.com/plugin/
"String processing, done right"


_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>