You can send bytes back to the client as an RPC response (it's just an HTTP request, after all) but the problem is what to do with the bytes once you have them. If you're willing to restrict yourself to browsers that support data:// URLs, you can send the image back as a data:// URL and just drop the result into an img tag. That approach excludes many (all?) versions of IE. As far as I know, the only IE that _might_ support data:// URLs is IE8. To be fully-compatible, you need to forge ahead with your existing approach or, as you say, generate a URL via RPC and make the generated URL resolve to the desired image.
If you want to fool around with the RPC infrastructure, you could possibly use a GWT-RPC request payload as the query parameter in a standard request, if you think such a representation would be more compact/useful than the representation you're currently using. On the server side, you could then use the RPC class (is that still in use?) to deserialize the parameters and drive the image request. Might be more trouble than it's worth, though. Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
