Thanks Thomas, that's the solution I was looking for too. The 'solution' I am using now to prevent the lookup before returning each object was to populate an 'ephemeral' object. I simply create a duplicate object using the same EntityProxy class and it returns to the client without doing the lookup.
Because the duplicate object is only returned for list searches I only partially populate it (to make it lighter across the wire) and it is stored in memcache so the performance hit is only for the first user. But it is a bit of a hack, so thanks again. Event ev = pm.getObjectById(Event.class, key); Event ephemeral = makeEphemeral(ev); returnEvents.add(ephemeral); searchCache.put(key, ephemeral); -- 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.
