synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera (JIRA)" <>
Subject [jira] Resolved: (SYNAPSE-62) Synapse should support transactional resource access
Date Mon, 12 Mar 2007 06:02:09 GMT


Asankha C. Perera resolved SYNAPSE-62.

       Resolution: Fixed
    Fix Version/s: 1.0-RC1

Done, all accesses to the registry (i.e. sequences, endpoints and resources) are now transactional
w.r.t this model. 

Hence a resource loaded from the registry for a message exchange will not see any updates
from the registry although the updated resource may be visible to other (new) messages that
arrive at Synapse later

> Synapse should support transactional resource access
> ----------------------------------------------------
>                 Key: SYNAPSE-62
>                 URL:
>             Project: Synapse
>          Issue Type: Improvement
>    Affects Versions: Incubating-0.90
>            Reporter: Asankha C. Perera
>             Fix For: 1.0-RC1
> Support transactional resources as follows: Once a key is looked up from a remote registry
during message
> processing, always keep a reference to it from the local message context.
> This way we are making sure that any subsequent reads for the same key will not fetch
a newer version off the
> remote registry as we will always pick the local reference from the message context.
Make sure that any responses for the request also see the same saved reference seen by the

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message