Bryan, >> If you're just updating certain "values" on a page, then returning a >native >> JS object makes a ton of sense. >> >> -Dan > >OK Dan....show me an example (I think I see where you're going, but that >situation...at least for the apps we build would be few and far between).
Ok, here's a very basic example using an old Client/Server Gateway JSAPI I wrote: http://pengoworks.com/workshop/js/gateway/example.cfm By just transferring back a valid JS object, not only are you streamlining the bandwidth, but there's really no reason to re-write the entire DOM since you're dealing w/very specific areas of the screen. You could easily rebuild this screen to allow you to edit records on the fly. NOTE: Mind you, I originally wrote this page in December of 2000, so it using older cross-browser techniques. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:244651 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
