If you want to support larger images (larger than 32kb) and/or IE6/IE7 you
have to use your current approach:
class MyImage implements Serializable {
String imageUrl; //which will point to your image servlet
AddtionalData addtionalData;
}
And in my opinion there is nothing wrong with it. You fetch all the data
you need in one GWT request and the browser then loads the image by its
Url. That way you got the additional data faster and you can already
display them while the image is still loading. Also using this approach the
browser can cache the image if the URL for the image does not change. If
you are trying to use base64 encoded images in a GWT response you always
download the image unless you cache it yourself.
-- J.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/O79TX6_cP6YJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
