Stuart Charlton wrote: > --- Steve Jones <[EMAIL PROTECTED]> wrote: >>Sorry for this, but I call snake oil. REST does not >>improve loose >>coupling, I still need to know the document formats >>and the URIs. > > Loose coupling != "no coupling". > > It's a lot looser than prior approaches, where you > also had to share the programming language (Java RMI),
As I've tried to stress here before, the new paradigm of RMI programming is available in Jini 2.0 and later. This paradigm is brought about by the Jini Extensible Remote Invocation layer which allows the invocation layer and endpoint/wire protocols to be abstracted and replaced without change to the software using RMI programming. Thus, there is no binding to programming language by choosing to use Java with RMI method calls when you utilize JERI. Instead, you are empowered to make many different changes in the way that you use the RMI programming model. You can use: o httpmd: protocol handler for jar file content validation and version control. o Kerberos/X.509 to hold off code downloading attacks. o Exporter and ProxyPreparer interfaces to allow layering of the RMI programming model behind application specific delegations. But wait, there's more... :-) Gregg Wonderly ------------------------ Yahoo! Groups Sponsor --------------------~--> Yahoo! Groups gets a make over. See the new email design. http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
