Good point Jon - I think selected serialization is the way to go... Joe also brings up a good point in that -- where do you draw the line from fully customizing an object vs simply creating a "return" object for the sake of simplification... ahh you have to love programming! :)
I just wanted to check first and see if there is/was something in the framework that I was missing.... In my senario I work using Ajax for building custom online mapping (think google maps) in my map object I have, as one example, a string dictionary collection that holds the layer info for the map - there is absolutely no need to bring this info to the client but it gets returned, in addition to everything else, everytime when all I really need is the map extent and a few other variables.... Ill trying selected serialization and post back here what I find out... thanks again, Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ajax.NET Professional" 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/ajaxpro The latest downloads of Ajax.NET Professional can be found at http://www.ajaxpro.info/ Don't forget to read my blog at http://weblogs.asp.net/mschwarz/ -~----------~----~----~----~------~----~------~--~---
