Transport mechanisms

[Jim Bethancourt]

Should supported transport mechanisms be outlined in the spec, or should that be limited to an implementation detail?  

The addition of Websockets to EE 7 got me to wondering if it would be a viable option as a transport mechanism between grid instances and if this should be mentioned in the specification or be implementation specific.

Thanks,

Jim

[Manik Surtani]

I presume you mean client -> grid transport?  The scope has always been for this communication to be in-VM.  In Infinispan we do support additional remoting techniques for clients to talk to remote grids too, but I'm not entirely sure whether that style of data access should be a part of this spec.  Anyone else have an opinion on this?

--
You received this message because you are subscribed to the Google Groups "JSR 347 discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jsr347+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Joseph Ottinger]

I don't think it should be part of the spec. Implementing containers should be able to provide mechanisms that support various transports.

--
Joseph B. Ottinger
http://enigmastation.com

Memento mori.

[Jim Bethancourt]

I was thinking grid transport across VMs (grid <-> grid) -- I didn't realize the scope for this spec only pertained to in-VM communication.

Thanks for the clarification,

Jim

[Manik Surtani]

Inter-node communication is probably best left as an implementation detail.

[Brian Martin]

I agree that the communications protocol should be an implementation choice.