[thelist] webapp logic
Jay Turley
JTurley at scottrade.com
Thu Jul 6 15:46:08 CDT 2000
I have developed some weblications which are single-page based. It's great
for a small tool. However, the group I work for is moving toward the
Model-View-Controller model of developing weblications. This does not lend
itself to creating single page apps.
refs:
http://www.javaworld.com/javaworld/jw-12-1999/jw-12-ssj-jspmvc.html
http://st-www.cs.uiuc.edu/users/smarch/st-docs/mvc.html
- Jay Turley --------
Quatrix, LLC.
http://www.qett.com
> -----Original Message-----
> From: David McCreath [mailto:mccreath at alaska.net]
> Sent: Thursday, July 06, 2000 3:53 PM
>
> I just downloaded a sample application this morning that lets you add,
> delete, or update records in an Access database using one ASP
> page, and
> changes appearance according to the action in the form using
> an IF statement
> for the value of the Request.StringQuery.
>
> ----- Original Message -----
> From: "Czechowski, Aaron" <aczechowski at towson.edu>
> To: "Thelist (E-mail)" <thelist at lists.evolt.org>
> Sent: Thursday, July 06, 2000 11:25 AM
> Subject: [thelist] webapp logic
>
> > All internal to one page or so.
> > What do ya'll think about that? Is there an advantage (process
> > speed, less connections, etc.) in having just one or two pages for
> > something, rather than having a multitude of pages, one for
> the initial
> > page, one for processing featureX, another for featureY, etc.?
More information about the thelist
mailing list