This would be easier I presume that trying to do it all in SQL. However,
one of the criticisms has been that the middleware is too complicated.
R
[EMAIL PROTECTED] wrote:
? a smart python data object with a dumb sql skeleton
*On Wed Dec 28 12:40 , Richard Hosking sent:
*
The gurus seem to be of the opinion that it is better to have
smart data
objects and dumb code to manipulate them.
R
Tim Churches wrote:
>
>>gnumed was originally concieved as "smart-server, dumb-client"
>>model, with backend triggers doing all kinds of high-level
stuff, like
>>interactions checking.
>>
>>
>
>I am now convinced that this is arse-about, putting the back-end cart
>before the horse, as it were. Better to put all the smarts in one
layer,
>the middleware, and use database back-ends in a dumb fashion, and
>thin-client Web interfaces (so the interface smarts are very closely
>integrated with the business logic in teh same set of classes in the
>middleware layer, which all runs on the server).
>
>
>
>
>
>
_______________________________________________
Gpcg_talk mailing list
[email protected]
<javascript:top.opencompose('[email protected]','','','')>
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
<parse.pl?redirect=http%3A%2F%2Fozdocit.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fgpcg_talk>
------------------------------------------------------------------------
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
