Hi rob,
If you're firing off a new thread I suggest you fire off this thread onto a
method of an object that your main application thread holds. That way you
can set some sort of state that both share and access. IOW, the new thread
can update a property on the object that the main thread can check or read
at some later point in time.
As Scott mentioned though, you'll want to be real careful with threads on
the server - there are lifetime issues that are very uh funky. It's Ok if
you create a thread and run it in parallel with your ASPX page thread, but
it gets tricky when your thread outlasts the main ASPX thread.
Generally a 'loading...' type page is better done via some sort of
asynchronous request that keeps refreshing until the task is done. This way
the Web Server is not tied up with this process.
Regards,
+++ Rick ---
--
Rick Strahl
West Wind Technologies
http://www.west-wind.com/ http://www.west-wind.com/weblog/
----------------------------------
Making waves on the Web
"Rob" <fi*******@att.net> wrote in message
news:54**************************@posting.google.c om...
In order to show a loading page, I am attempting to call a function as
part of a new thread, my issue is that the function returns a boolean
if it is succesful since it also calls other functions,,
how can I start this function in its own thread, yet get back its true
or false to know it succeeded?
thanks in advance
r