Json Object Size?
i have this user interface for a client that i have to mod (The UI is a link crawling monitoring for his website), the present one uses php database connection for every single action that is done on the UI (select link to be monitored, show link stats etc...) what we want to do is to have the links retrived from the database stored in a json object while the client is playing with the links on the UI (making all kind of editing actions) and then when he want to store all the modifications/actions he has made then the data stored in the object are sent back to the database...
One of my coworker's (he's a java and O.O. programming specialist) objection to that is that there are too many links (data) to put in a simple Json object... and it will be then difficult to store all the actions made on the json object because there will be too many info/data for it to handle etc...
don't know if i am clear... but if someone want to throw his two cents do not hesitate to PM!
I would say that your co-workers concerns seems valid. If you transfer a lot of data to the client side, you will have to synchronise that on the server side.
I'm not sure I understood you properly though - What's the reason that you want to use this strategy?
the reason i want to use this strategy (if only my english was good enougfh to xplain it well) is that my boss want ti done that way so we can have a very cool ajax drived User Interface for our clients who are tired of the flat User Interface that we have right now...