Kevin
Almost everyone using OO techniques struggles with this exact problem and it's not specific to AJAX - how do you mix the "View" with fully populated objects. For example, you may have a web page that needs only to display summary information about an order, yet a fully populated order could contain 1000 line items. Seems like a lot of overhead to load a full order object with all the line items for no reason. This is a similar scenario that you're describing with Ajax. Joseph raises a good point, introduce "view objects" into your architecture, you might find that this is ultimately your easiest route. However, I would suggest looking into building custom converter that inherits IJavaScriptConverter. You can override the Serialize method to do some custom serialization. This is your pipeline into the Ajax framework. From there, I think good old reflection and .NET attributes would allow you to only serialize the properties you like.
On 8/8/06, o0JoeCool0o <[EMAIL PROTECTED]> wrote:
well either way you would have to tell it what to limit which is the
same amount of work as saying
myArray(0) = myObject.property1
myArray(1) = myObject.property2
myArray(2) = myObject.property3
and so on...
--~--~---------~--~----~------------~-------~--~----~
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/
-~----------~----~----~----~------~----~------~--~---
