You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Mark Brouwer (JIRA)" <ji...@apache.org> on 2007/12/13 17:06:43 UTC

[jira] Updated: (RIVER-275) implement RoundTripTimeout constraint

     [ https://issues.apache.org/jira/browse/RIVER-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Brouwer updated RIVER-275:
-------------------------------

          Component/s: net_jini_jeri
    Affects Version/s: jtsk_2.1

> implement RoundTripTimeout constraint
> -------------------------------------
>
>                 Key: RIVER-275
>                 URL: https://issues.apache.org/jira/browse/RIVER-275
>             Project: River
>          Issue Type: New Feature
>          Components: net_jini_core, net_jini_jeri
>    Affects Versions: jtsk_2.1
>            Reporter: Martin Cornelius
>
> In realtime scenarios it is often desirable to know, if a remote call can be executed within a certain duration, that is specified by the caller before making the call. If the complete call cannot be executed within the specified duration, it should return to the calling thread with an indication that a timeout occured.
> In CORBA terminology this feature is called the RoundTripTimeout Policy. It would be nice to have something similar in JINI. A possible implementation could be a new invocation constraint class, perhaps named net.jini.core.constraint.RoundTripRelativeTime. This class could implement the same interfaces as net.jini.core.constraint.ConnectionRelativeTime, and could also have a constructor taking the desired timeout as argument.

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