Fire and forget URL

[Ashley Finney]

In GAE I want to fire a Post message at a URL but I do not want to wait for the response, the call should be as quick and cheap (cpu/memory/cost) as possible.  All I'm doing is using this to send a message to another server.  I don't mind if I lose messages.

Instead of using "appengine/urlfetch" is there another method?

Many thanks.

[Chad Vincent]

There is an Async method on the URLFetchService (in Java, at least) that you can call and just never process the Future.

URLFetchService.fetchAsync(HTTPRequest)

[Christian F. Howes]

note that if you use the urlfetch async (which was going to be my suggestion as well) that you do need to wait at the end of your request handler for the future or the request will be killed if it hasn't completed yet.

[Barry Hunter]

Maybe you could use the Task Queue? inserts should generally by quick. 

Then a 'worker' can process tasks in background - performing the actual POSTs 

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/f2962eeb-8fb7-4880-865d-ceaabb93bfc3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Barry Hunter]

Or maybe even use XMPP, to 'chat' with itself. 

https://cloud.google.com/appengine/docs/java/xmpp/

The front end just sends a chat message. 

The backend worker subscribes to the channel, and performs the POSTs

[Alex Martelli]

Not sure what advantage you'd envision for XMPP here -- this kind of job (handing out a task to a worker) is exactly what task queues were designed for.

Alex

To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAJCAUuJYCSksmDhzy5SnN8Nh%2BzSGPQfPiRzZKvA8th02eg94Tg%40mail.gmail.com.

[Barry Hunter]

Possibly no real advantage, just an alternative :)

I suppose, there is a small risk of exceeding the Task Queue storage free quota, but seems unlikely. 

To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAE46Be8U--uj3pZ1%3D%2B3SD4dhLBwq%2BbziPj8dCxBCrzP8beh8VA%40mail.gmail.com.

[Chad Vincent]

It's why you don't put any significant payload in the Task.  You put it in a Datastore entity and use the key as the payload.

Or if you really don't care if it fails, put it in Memcache and use the key as the payload.