ws-scout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anil Saldhana (JIRA)" <>
Subject [jira] Commented: (SCOUT-12) Implement the Asynchronous Registry Request Feature
Date Wed, 12 Apr 2006 16:34:19 GMT
    [ ] 

Anil Saldhana commented on SCOUT-12:

A note I sent to the scout-dev team:

  the JAXR 1.0 Specification in Section 7.5 has the following to say about "Asynchronous Connections".

"If the communication preference is asynchronous, each request method call returns a non-null
JAXRResponse (or a sub-interface) immediately. The JAXR provider may spawn a separate thread
to process the client request asynchronously."

What this means for Scout is that we will have to retrofit all the request methods for asynchronous
processing, an exercize I am reluctant to perform at this moment.

This feature is the only one that is missing from Scout to claim full JAXR 1.0 compliance
for Level 0 Capability. We already have J2EE 1.4 Compliance for JAXR.

Unless there is someone who embeds Scout other than in an J2EE Application Server (where this
async feature is not mandated) and wants this feature, I am going to defer this "Async Connections"
indefinitely (


If you want this feature, vote on it.

> Implement the Asynchronous Registry Request Feature
> ---------------------------------------------------
>          Key: SCOUT-12
>          URL:
>      Project: Scout
>         Type: Task

>   Components: Scout Implementation
>     Versions: v0.5
>     Reporter: Anil Saldhana
>     Assignee: Anil Saldhana
>      Fix For: 1.0

> JAXR 1.0 Specification mandates an asynchronous registry request, which Scout needs to
implement to claim JAXR 1.0 compliance (Level 0)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message