This sounds like a unique and workable answer. If your cookie size does not exceed 4k you should be fine. The only thing I don't know is how the browsers will handle a statically named cookie with asynchronous request. Even though Javascript (GWT) is single threaded the browser is not. Try to queue your requests that use this method.
On Jan 7, 7:56 pm, AB <[email protected]> wrote: > I am thinking about a charting app that will use jfreechart on the > server side (I need PDFs and other server side output anyway) and GWT > + Canvas on the client so that users can do fancy things like curve > fit in the browser. > That means that when the client asks the server to render a chart, the > client needs to get back a png and also some data (like scaling info, > etc). I can of course do 2 rounds trips but I am thinking of > combining it into one rt. > > The idea is that the server response is an image/png but also sets a > nonpersistent cookie in the header that encodes the data I need. The > gwt app disassembles the cookie value (perhaps it is even json). If > the cookie would be too big (unlikely), the cookie value becomes a > message to the client that it needs a dedicated rt. > > Does anyone see a problem with this? Any thoughts are appreciated. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
