I was hoping to get an analysis of what happens inside the marshalling machinery if a "void" is executed from the client or description of a technique that does exactly this by design.
Failing that I'll get back to it in a couple of days and test out the approaches that make sense to me. Mike Gale -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ricardo Sent: 2009/04/9 8:57 To: jQuery Development Subject: [jquery-dev] Re: Fire and Forget requests using jQuery What would be the downsides of sending a POST and ignoring the response? $.post('/errors', {errorType: 'xx', status: 'etc'}) On Apr 5, 11:55 pm, Mike Gale <[email protected]> wrote: > I have some non-critical logging messages I want to send from > browsers. > > I don't want the browser to wait for a response, or use up an > available xhr channel. > > The rest of the app is jQuery talking to a webservice on the server. > > XMLHTTP is, as far as I know, a protocol that assumes you want a > response and has no mechanism for fire and forget. I could set up > JavaScript code that aborted the xhr, maybe on status changed, but > that seems kludgy. > > As far as I know, there is no native jQuery way to send a "fire and > forget" message. > > What ways are suggested to achieve this, preferably using jQuery? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
