Skip to main content

[jsr339-experts] Re: Async API Usage Guidance

  • From: "Markus KARG" <markus@...>
  • To: <jsr339-experts@...>
  • Subject: [jsr339-experts] Re: Async API Usage Guidance
  • Date: Sun, 30 Sep 2012 22:40:10 +0200
  • Organization: HeadCrash

Jan,

I think you could say that all APIs which are potentially blocking are
long-running. Obviously all of them will benefit from async operation.

Regards
Markus

> -----Original Message-----
> From: Jan Algermissen [mailto:jan.algermissen@...]
> Sent: Sonntag, 30. September 2012 22:31
> To: jsr339-experts@...
> Subject: [jsr339-experts] Async API Usage Guidance
> 
> All,
> 
> based on the implementation experience with the Async API to date, can
> you provide advice on what a developer should consider a 'long running
> operation'?
> 
> What operations are usually long running enough to see a server
> performance or capacity gain when switching to the async API?
> 
> File IO?
> JPA data read?
> JPA data write?
> Upstream HTTP request?
> ...
> 
> 
> Jan



[jsr339-experts] Async API Usage Guidance

Jan Algermissen 09/30/2012

[jsr339-experts] Re: Async API Usage Guidance

Markus KARG 09/30/2012
 
 
Close
loading
Please Confirm
Close