Re: newbie: javaspace implementation protocols used

Xaea,



GigaSpaces provide ability to implement your own "protocol" as the transport
layer between the client and the space and also between the spaces
themselves when replicating data in clustered environment.



Another much more simple approach to access the space can be done via Mule
ESB.

See:

http://www.grid.org.il/_Uploads/500mule-JavaSpaces.pdf

http://mule.codehaus.org/

http://www.gigaspaces.com/download/GigaSpaces-Mule_Enterprise_Service_Bus_fo
r_Stateful_Service-Oriented_Architectures.pdf



ESBs provide a messaging abstraction layer, enabling distributed
applications to easily communicate with each other using a variety of
transport mechanisms. SymphonySoft's Mule is a popular open-source product
that implements the ESB model. Unlike traditional messaging approaches, the
Mule ESB addresses a dynamic environment in which services can come and go,
and communicate with each other on an on-demand basis and in an associative
manner, based on content and using different transports depending on the
application (end-point) requirements. This paper provides a short
description on how to use the GigaSpaces Enterprise Edition software as an
Enterprise Service Bus (ESB) runtime environment using the SymphonySoft's
open source Mule ESB framework.



Please note GigaSpaces allows also .Net and C++ application to access the
space and share and exchange objects with Java application. This is done via
our .Net and C++ JavaSpacs libraries.



The default transport protocol using sophisticated protocol based on NIO we
have developed.



Best Regards,

        Shay

----------------------------------------------------

Shay Hassidim

Product Manager, GigaSpaces Technologies

Website: www.gigaspaces.com <http://www.gigaspaces.com/>







-----Original Message-----
From: xaea alvein [mailto:[email protected]]
Sent: Thursday, May 04, 2006 7:10 PM
To: [email protected]
Subject: newbie: javaspace implementation protocols used



from what i read at artima website, it seems that if i am to create a

javaspace implementation that is reachable by clients using RMI, RPC, or

CORBA, then it is my responsibility to create an implementation of javaspace

that uses those protocols. it depends on me and my implementation, not how

the clients try to connect to my javaspace implementation. is it true?



then another questions that bother me, is outrigger using jeri as its

protocol? and i want to know what kind of protocol used for another

implementation, like gigaspace, or tspace. is there any javaspace

implementation using RPC or CORBA or another well-known protocols? is it

possible to create an implementation that can be reached by multiple

protocols, say, RPC, RMI, and CORBA altogether?



===========================================================================

To unsubscribe, send email to [email protected] and include in the body

of the message "signoff JAVASPACES-USERS".  For general help, send email to

[email protected] and include in the body of the message "help".



To view past JAVASPACES-USERS postings, please see:

http://archives.java.sun.com/archives/javaspaces-users.html


===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html