[TransWarp] Requirements for the future peak.messaging package

[Ulrich Eck]

Hi Phillip,

> Well, as with JNDI, I'd probably look at the Java API docs, and try to
> figure out what parts could be taken out.  In the case of JavaSpaces I
> don't think there's a lot to take out.  JavaSpaces was built "up" from
> the Linda concept, and is not really a J2EE API; technically it's in the
> "Jini" sphere of technologies.
>
> JavaSpaces basically just adds objects and transactions to Gelernter's
> "Linda" language.  My thought is that adding this to PEAK would probably
> be done by a specialized interface available on Racks to "put" or "take"
> objects.  Or perhaps they should be called "Spaces" in that event.  The
> actual internal implementation would likely be just adding a lock manager
> and local queue for transient objects, to an existing PEAK persistence
> mapping to a DB or something else.
>
> Of course, this implies that the PEAK persistence machinery needs to
> exist, first.  :)  So I'm not going to put a lot of effort into
> designing, at this stage, what the "spaces" extensions would look like,
> since it's likely to change as the persistence and transaction API's
> evolve.
>

.. you're probably right :) ..

so let's work on persistence first .. we'll be busy till mid of September,
then we will be back developing our stuff and hopefully start migrating
to peak ..

cheers


Ulrich Eck
------------------------------------------------------------------------
net-labs Systemhaus GmbH
Ebersberger Str. 46
85570 Markt Schwaben
fon:   +49-8121-4747-11
fax:   +49-8121-4747-77
email: ueck at net-labs.de
http://www.net-labs.de