Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / November 2007

Tip: Looking for answers? Try searching our database.

Server Side Notifications and a Javascript Application...

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Spam Catcher - 30 Nov 2007 05:17 GMT
Hello Everyone,

I'm building an application which requires server side events to be pushed
to clients.

Typically I build these applications with a think client, but the machines
I'm deploying this particular application have a very slim image - no .NET,
Java, or any other runtimes.

I am only able to use Internet Explorer 6.0 (running on Windows 2000 Pro).

I've implemented a solution using web services, a polling mechanism, and
ASP.NET AJAX ... however this method takes up a lot of CPU cycles on the
client which is noticable since javascript is single-threaded. I am polling
the server every second.

I understand there is an up and coming framework called COMET which does
provide server side event pushed through a persistent connection, but does
anyone know how easy it would be to integrate this pattern into ASP.NET
Ajax?

I'm just throwing this out to see how other people have built applications
which require a server side event push.

Thanks!
Nick Chan - 30 Nov 2007 06:19 GMT
hi at matlus dot com there's "always connected" http thingey written
in delphi. client is always connected. i wonder if it helps to achieve
what u want

> Hello Everyone,
>
[quoted text clipped - 21 lines]
>
> Thanks!
bruce barker - 30 Nov 2007 06:57 GMT
comet uses what used to be called server push. basically the browser
does a request usually to a iframe. the server keeps the connection open
for a limited time, say a minute and pushes javascript events via
script. you want to reload to free memory in the browser and to prevent
timeouts.

<iframe src="push.aspx">

push logic

Response Buffer Off
Response.Write("<script>")
loop
 wait on event
 if (timeout)
    Response.Write("document.location.href = 'push.aspx'")
    Response.End()
 else
    Write event javascript
    Response.Flush()
end loop

-- bruce (sqlwork.com)

> Hello Everyone,
>
[quoted text clipped - 21 lines]
>
> Thanks!

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.