RE: ASP design issue

************************
Mike Carlson
http://www.domitianx.com
domitianx(at)domitianx.com
************************ 

-----Original Message-----
From: Mike Carlson [mailto:domitianx(at)domitianx.com] 
Sent: Tuesday, August 14, 2001 9:29 PM
To: 'Emerald Spirit'
Subject: RE: ASP design issue


If its only 5 pages doing simple add/edit and deletes, why use a servlet
at all?

You are looking at a 10 to 12 lines of code max for each db function.

As for the login, use IIS user permissions or a simple user table to
validate against.

Something like you are doing should take less than a day or so to put
together.

If you really NEED to use a servlet, then I would suggest one servlet.
The reason is that object instantiation is extremely expensive as far as
resources go. If you can instantiate the object once, perform a few
different functions on it and then destroy, then you will save the
overhead of creating and destroying the servlet multiple times.

But I REALLY don't think you need to create a servlet for it.

************************
Mike Carlson
http://www.domitianx.com
domitianx(at)domitianx.com
************************ 

-----Original Message-----
From: owner-hwg-techniques(at)hwg.org [mailto:owner-hwg-techniques(at)hwg.org]
On Behalf Of Emerald Spirit
Sent: Tuesday, August 14, 2001 7:51 PM
To: hwg-techniques(at)hwg.org
Subject: ASP design issue


Hi all!

Forgive my ignorance.  I generally have senior
programmers on the same project as I to answer some of
these mundane questions.  Unfortunately this time I am
the only programmer on this project and have nobody to
bouce ideas off of.

I have a design question.  I'm working on creating a
simple front-end to a database application --
basically a simple trouble ticket solution.  It'll
consist of about 5 dynamic pages or so... there will
be various points in the application where the
database will need to be updated, queried, and new
records created.

We've decided to use ASP on IIS on an NT4.0 server
hitting against a SQL Server v7.0.  The site will
require a login which I was planning on creating a
Java servlet for.

I'm looking for suggestions on back-end processing. 
We need to keep the database code separate from the
HTML as much as possible.  So I generally create
servlets etc (of course I  normally do JSP not ASP) 
All updates and changes will occur to the same
database.  T

he question is -- would it be better to make one
servlet that depending on parameters can do multiple
tasks or have multiple servlets each specialized to
its own task??  Is there a better way to do this -- my
brain does become muddled late in the day and its
entirely possible I'm glossing over a very simple
solution.

Any help would be appreciated.

TIA
Rebecca

=====
Do while Project<>Completed
   if impossible = true then
      rethink(approach)
      set impossible = false
   end if
loop

__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA