Thanks for the suggestion; I think gwt4air is for the client side; what we need is actually a way to make GWT RPC understand AMF3 requests from already implemented clients, the actual JEE implementation is done at GraniteDS but it would make no sense to have it running for GWT adding all this extra overhead just for the AMF compatibility, the another solution would be to leave JEE and go for AMFPHP.
But a good chance would be to extend the GWT protocol in order to have an RPC which understands the AMF3 requests without adding extra complexity to the project itself. Best regards, Carlos. On Aug 16, 1:27 pm, Juan Pablo Gardella <[email protected]> wrote: > Are you look gwt4air? > > 2011/8/16 Don Rudo <[email protected]> > > > > > > > > > Hello I'm looking for a way to extend the GWT-RPC protocol in order to > > make the RPC service able to be used from more products (more specific > > flex and flash products). > > > The intention is to be able to use GWT RPC for applications using the > > Action Message Format (AMF 3) which specification is open source and > > according to this benchmarks ( > >http://www.jamesward.com/2007/04/30/ajax-and-flex-data-loading-benchm... > > ) it's a very efficient RPC protocol. > > > Best regards, > > > Carlos. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Web Toolkit" 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/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
