Leaving the absurd bike-shedding about licenses to the side for a moment.. I don't really get the zen of GPG/IMOP/Meso.
You compare it to REST -yet it seems to be an RPC mechanism though and through. If I may be so bold (and I probably misunderstood) you seem to make the classical error of so-called "low REST" viz. programming the web via RPC, not resources. I feels more like SOAP, but with "lazy" retrieval of types (rather than up front in some wsdl etc) and json instead of xml -and meso brings to mind F# type providers Beyond that, what does it do (that SOAP doesn't)? Does the client push code to the server? (eg PUT+ EVAL in place of PUT + GET) Does one create remote persistent objects? It seems odd to me to expose the protocol in a user friendly way (a la REST over SOAP) and then bury it again in a compiler. I await embarrassment at having missed the point :-) Pete F -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
