This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Yep, it helped a lot on the implementation specifics.
However, I found it leads to memory leaks, as I have an object being created by a third party that I was intending to transmit as JSON then update it with some info received via Ajax.
The update part just seems to add another object and won't match up in memory correctly.
However, using a wrapper allows me to save the memory pointer properly so that I am assured of addressing the same object, also reduces network overhead as I only need to send relevant parts of the data object instead of all of it.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com