Do you think is it a bad idea to use SerializationStreamWriter and SerializationStreamReader to write an object's state to the history? It seems like it would be a more convenient way to go than for me to try to write my own methods for doing this. I guess it could be a problem if I blow past the URL length limit but I suppose that is a possibility with my own serialization schemes too.
Thanks in advance for your advice -Keith --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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 -~----------~----~----~----~------~----~------~--~---