@Scott: I don't think this is the same thing. The dialog box is in the same memory space as the rest of the app and can freely share data without serialization/de-serialization, is written in the same language, uses the same frameworks, and so on.
I'd argue that this was an implementation detail rather than a key requirement, but it's otherwise a distraction from the question at hand.
The core issue is how confident you are moving your business logic down to the client. If your data is well secured, then I'd argue that there's no risk going the whole hog and having everything on the client. If the data in the database was well secured, then I'd have no trouble opening up SQL access directly to the client, giving you the world's smallest server side component.
Alas most shared-hosting environments seem to be designed to not allow this - inasmuch as you usually only get a single database login with db admin privileges.
Oh yes, and PHP is truly horrible. Watch out for the magic quotes stuff.
by Andrew Barry — Aug 03
I'd argue that this was an implementation detail rather than a key requirement, but it's otherwise a distraction from the question at hand.
The core issue is how confident you are moving your business logic down to the client. If your data is well secured, then I'd argue that there's no risk going the whole hog and having everything on the client. If the data in the database was well secured, then I'd have no trouble opening up SQL access directly to the client, giving you the world's smallest server side component.
Alas most shared-hosting environments seem to be designed to not allow this - inasmuch as you usually only get a single database login with db admin privileges.
Oh yes, and PHP is truly horrible. Watch out for the magic quotes stuff.