Jeff Gutierrez writes:

> But there's a caveat in putting everything in the database..  A few years
> back, DB companies were evengelizing that the DB should be the repository
> of all information presented in the web page.. Pretty interesting piece
> but early adoptors soon learned that doing so required tons of resources
> from the database, which made then slow as hell.  On example of this is
> Informix' Web DataBlade.  

>From what I heard, Illustra+DataBlade (which, for a while, was downloadable
free with AOLserver) was very prone to deadlocks at high volumes (each page
was a transaction, and an INSERT/UPDATE on one page would lock up if more
than one user was requesting that page at the same time). Or so I've read.
You can ask your friends that worked on Illustra about that and the other
horror stories on http://philip.greenspun.com/wtr/illustra-tips

These days, of course, pretty much everything, content-wise, is stored in a
database. Slashdot and gra.ph uses MySQL. Most big e-commercial sites use
Oracle or MSSQL.

> This is the very reason why application servers came about.. so there can
> be separation of presentation generation (JSP, ASP, PHP) from the business
> logic, and the database.  

I don't think application servers really solve anything for web apps. It
just becomes another layer of complexity that has to be understood,
documented and maintained by already overworked programmers. Essentially,
your business logic is dictated by your data model and the forms you
provide to represent the valid transactions.

> An alternative that I can suggest to Orly is JavaServer Pages (JSP) Custom
> Tags. JSP custome tags are actually vanilla JavaBeans that are called by
> the JSP engine whenever encountered.  Here's a possible JSP tag lib:
> 
> <XX_FORM name="pangalan" sqlview="SELECT first_name, last_name">
>   <XX_INPUT type="text" displayname="First Name" sqlfield="first_name"/>
>   <XX_INPUT type="text" displayname="Last Name" sqlfield="last_name"/>
> </XX_FORM>

I'm a big KISS advocate. Orly knows relational design. Orly knows Perl and
DBI. Let Orly design the basic data model and code the logic in Perl/DBI
for Apache. Then I can steal his datamodel and code the logic in Tcl. You
could steal the datamodel and write JSPs for it. Someone else could code it
in PHP or Python, etc.

I'd say we'd get a lot more done than if Orly had to hunker down to learn
Java, JSP, JavaBeans, JavaFoo, JavaBar, etc. to write a relatively simple
form generator.

Brian
P.S. the default Reply-To field is wrong, should be [EMAIL PROTECTED]
and not [EMAIL PROTECTED]
--
Brian Baquiran <[EMAIL PROTECTED]>
http://www.baquiran.com/  AIM: bbaquiran 
Work: +63(2)7182222       Home: +63(2) 9227123

I'm smarter than average. Therefore, average, to me, seems kind of stupid. 
People weren't purposely being stupid. It just came naturally.
                              -- Bruce "Tog" Toganazzini
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]

Reply via email to