Re: The MySQL/PHP pair

Dawn M. Wolthuis wrote:

> We also have some agreement
> (at least I know you agree with me on this one) that we need a means of
> encoding constraints once for the front-end and back-end "services" to use
> the same constraint specifications, or even the same constraint "engine".
>

Just jumping in to bang my same old drum.

The phrasing "...the same constraint specifications..." is strong because the only way to have them both share the same specs is if the authoritative copy of those specs is outside of both. Also, it would be much easier to do this if those specs were data instead of code.

Also, adding automation to the specs instead of just constraints would greatly enhance their value.

Less intriguing is the phrase "...or even the same constraint 'engine'". This may be a perfectly wonderful idea but I'm having a bad first impression. Sounds like trying to reproduce the server on the client, which is bad, because only the server can be the server.

4 the FAQ: Laconic2 and I have previously come to quick agreement, and I believe he beats this drum from time to time, that the client should implement any biz rules that can possibly aid and assist the user, including some constraints, but that can only cut down on what is submitted to the server, and cannot prevent submissions that ultimately will be rejected.

In the spirit of the OP, With PHP and MySQL, implementing biz rules could be limited to the PHP layer, which is the server as far as the users are concerned. It that beyond which they may not pass. Putting biz rules in the client means the browser. Now it becomes even more important to have the biz rules in data if you are going to start supporting all of these different platforms.

-- 
Kenneth Downs
Use first initial plus last name at last name plus literal "fam.net" to
email me