long-polling

Is it possible to take an HTTPServletRequest away from its thread, dissolve this thread (i.e. bring it back to the pool), but keep the underlying connection with the browser working, until I get the results from a time-consuming operation (say, processing an image)? When the return data are processed, another method should be called asynchronously, and be given the request as well as the data as parameters. Usually, long pooling functions in a pretty blocking fashion, where the current thread is not dissolved, which reduces the scalability of the server-side app, in terms of concurrent

I am using .ajaxStart() and .ajaxStop() to show a modal while an ajax request is being made. (between start and stop) Now I'd like to add a longpoll function that keeps waiting for notifications, similar to the one on the left upper corner of this site. My problem now lies in disabling this modal only for the longpolling request.. Registering "loading screen" on and off handlers: $(document).ajaxStart(handleAjaxStart); $(document).ajaxStop(handleAjaxStop); My longpoll function: $.ajax({ timeout: 35000, url: longPollUrl, success: function(data){ if(data.queCount) $('#numQueCount').html(data

I am writing a server for an iOS game. The game is turn based and the only time the server needs to push information to the client is to notify of the opponent's move. I am curious if anyone could comment on the performance and ease of implementation differences between using websockets and long polling. Also, if I used websockets, should I only use it to receive information and send POST requests for everything else or should all communication be through the websocket? Additionally, is there anything to extra to consider between websockets and long polling if I am interested in also making a

I know there are ways to fake it, polling (or long polling) but is there any way to have the server contact the browser to push out information? Either polling option wastes resources on the server and depending on the server can lock it up (apache and iis for example). Seems like a lot of sites are using long polling to fake a server-side push mechanism over http. Wouldn't it just be better to have a true push protocol built into a browser? What options are there that are server friendly to push (fake or otherwise) information to web browsers? I know there are ways to fake it, polling (or

This question already has an answer here: Comet implementation for ASP.NET? [closed] 8 answers Does anyone know how to code up long-polling AJAX requests (for server PUSH notifications) in ASP.NET MVC? Whenever I do it, it seems that only the last browser to open up a window gets the notifications. As if IIS/ASP.NET were canceling the last request because it was hung or something. Jacob I recently wrote a simple example of a Long Polling Chat Server using MVC 3 Async Controllers based on a great article by Clay Lenhart You can use the example on a AppHarbor deployment I set up based on the

see also " WCF push to client through firewall " I need to have a WCF client that connect to a WCF server, then when some of the data changes on the server the clients need to update its display. As there is likely to be a firewall between the clients and the server. All communications must be over HTTP The server can not make an (physical) outgoing call to the client. As I am writing both the client and the server I do not need to limit the solution to only using soap etc. I am looking for built in surport for " long polling " / " Comet " etc Thanks for the most informative answer from Drew