Claudia Fong wrote:
I want to be on server side...
I don't want to write javascript
Doing something server side every N second does not
fit well with the ASP.NET model.
Options I can see:
1) Start a thread (like in global.asax Application_Start) that
updates some global data (like stored in a singleton) every N
second and pages gets info from that global data.
2) Run a Windows service that has the thread that updates some
data every N seconds and have pages request info via
a low overhead protocol (remoting, plain sockets etc.).
#1 is not good (in general it is not good to mess around
with threads in a context where the container manage threads
and there will be extra work to get it to work well over web app
restarts) and #2 is rather complex, but I think
that is the options.
Arne