I'm using RequestFactory for a 'non-data-orientated' app and its works
very nicely.
Chained method invocation:
MyServiceRC serviceRequest = appRequestFactory.MyServiceRC();
serviceRequest.giveMeAString().to(stringReceiver);
if (needPojo == true)
serviceRequest.giveMeAPojo().to(pojoReceiver); // Pojo would be a
ValueProxy for example.
// Now fire both methods in one RPC request, and do whatever
processing we want once both completed.
serviceRequest.fire(processStringAndPojoReceiver);
A pretty nice way to call server side methods. You are certainly not
restricted just to persisting and retrieving datastore objects with
RequestFactory.
On Thu, Jul 14, 2011 at 10:36 AM, Michel Jonker
<[email protected]> wrote:
> Hi,
> This is a cross post from the AppEngine group, but since I got no
> response there, I want to try this group.
>
> I am trying to figure out the best practise to consume my App Engine
> services from both Android and GWT.
> Since the services are not that data oriented, I first considered GWT-
> RPC.
> But given the fact that the GPE 2.4 sample project voor Android comes
> with
> RequestFactory, I am leaning towards this approach.
> I was hoping someone could validate this 'best practise' :
> When you have both Android and GWT consumers of your App Engine
> service,
> apply the RequestFactory pattern.
>
> TIA
>
> Michel Jonker
>
> --
> 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.
