Comments for Caffeine Lab

Comment on Asynchronous HTTP Client in Play Framework by Arno.Nyhm

Arno.Nyhm — Wed, 07 Jul 2010 18:00:13 +0000

maybe you can give the callback also a helper object which holds more informations and also the response object (which is still open until the last callback is used).

Comment on Asynchronous HTTP Client in Play Framework by erwan

erwan — Thu, 01 Jul 2010 08:30:06 +0000

Arno: Actually, there’s no closures in Java so no callback functions. I could however expose a function that takes an interface with the methods “onSuccess”, “onError” and so on, then people can define a class on the fly.

However that wouldn’t help if you want to return a response to the user after you get the result. That would only replace usage of jobs.

Comment on Asynchronous HTTP Client in Play Framework by Arno.Nyhm

Arno.Nyhm — Thu, 01 Jul 2010 00:35:56 +0000

why you dont use a callback function with the async call?

Comment on Asynchronous HTTP Client in Play Framework by sakuraba

sakuraba — Wed, 30 Jun 2010 09:07:42 +0000

Thanks for clarification.

Comment on Asynchronous HTTP Client in Play Framework by erwan

erwan — Wed, 30 Jun 2010 08:24:31 +0000

sakuraba: the waitFor is better that the synchronous call because it doesn’t block a Play thread for the time it’s waiting (and it could be several seconds). On a heavy traffic site the first visitor will block an execution thread, the second block the other thread and all the others will be queued. At the end of the day instead of waiting just for his request to the web service, the user has to wait for a thread to be freed and it can take a long time.

Now for the waitFor vs. a job: it depends what you’re doing. If it’s a general information (like the twitter box on Planet Play) a job is better. However if the WS is really specific to the visitor’s request, and you need to provide feedback, you can’t use a background job.

Example: your web application is a feed reader, and you want to provide a “refresh now” button. You’ll want to refresh your view of the feed after a success, and notify the user if the feed couldn’t be retrieved. You can’t notify the client of a success with a background job so you have to use waitFor (or use a synchronous call).

If you’re doing that in an AJAX call, then you can simply show a throbber and the user can still interact with your page during that time.

Comment on Asynchronous HTTP Client in Play Framework by sakuraba

sakuraba — Wed, 30 Jun 2010 07:12:06 +0000

Nice article, but I dont get the idea.

How is an async “wait” method better than a long running synchronous call? At the end of the day the user will have to wait in both scenarios

Or can you render something to the user while “waitfor” is executed?

It seems to me that a Job-based solution is the best one after all.

Comment on Asynchronous HTTP Client in Play Framework by Serdar Irmak

Serdar Irmak — Tue, 29 Jun 2010 18:31:20 +0000

Well done, I love open source.

Comment on Asynchronous HTTP Client in Play Framework by grenlibre

grenlibre — Tue, 29 Jun 2010 17:32:48 +0000

This is pretty cool for mashup Play application using multiple API.

Thanks

Comment on Asynchronous HTTP Client in Play Framework by Nicolas Martignole

Nicolas Martignole — Tue, 29 Jun 2010 16:01:59 +0000

Great post about one of the most interesting feature of Play! framework.

Thanks for your job Erwan

Nicolas.

Comment on Testing in Play’s Eclipse Plugin by Damien B

Damien B — Tue, 16 Mar 2010 22:55:54 +0000

Rassurant Faudra que je teste un jour. Faudra trouver le projet qui s’y prête par contre.