[
https://issues.apache.org/jira/browse/RIVER-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Grahn updated RIVER-385:
------------------------------
Priority: Minor (was: Major)
> Provide for the local instantiation of a Javaspace without services
> -------------------------------------------------------------------
>
> Key: RIVER-385
> URL: https://issues.apache.org/jira/browse/RIVER-385
> Project: River
> Issue Type: Wish
> Components: com_sun_jini_outrigger
> Reporter: James Grahn
> Priority: Minor
>
> Suggestion from Jeff Ramsdale:
> I'd like to be able to work with a Space without having to mess with Jini's
> service starter. If I could instantiate a space locally and control its
> lifecycle in my app it would be easy to use it (say) in the context of unit
> testing my components or as an embedded message broker in my app.
> ---
> I second this. I believe some implementations of the Javaspace interface do
> provide some measure of this functionality already, though Outrigger does not.
> Note that this is specifically regarding the implementation, outrigger, and
> not the protocol/interface layer Javaspace. On face value, it's not
> unreasonable for the implementation to provide for a remote/service layer and
> a core datastructure that the remote layer perhaps also uses. Not sure how
> easy to implement it would ultimately be.
> ---
> Use cases:
> 1) Unit testing of Javaspace-enabled code.
> 2) Enabling the use of Javaspace as a local datastructure for message
> passing, object discovery, etc. May also be useful for coordination between
> threads.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
