AS Libraries for stay-open CGIs
AS Libraries for stay-open CGIs
- Subject: AS Libraries for stay-open CGIs
- From: SeaSoft Systems <email@hidden>
- Date: Fri, 16 Feb 2001 09:55:24 -0800
I am thinking about tidying up several (five or six) stay-open
Applescript CGI's I wrote for a Webstar server. Replicated in each
CGI of the collection are identical handlers which are currently
hard-coded within each CGI, which produces a set of stand-alone CGIs,
each requiring no other library or script resources.
This is obviously a situation in which a single stay-open library of
utility handlers accessible to all the CGIs is very attractive from
the point of view of tidy coding and maintenance.
However, particularly in a server environment in which CPU cycles are
precious, there is a tradeoff between:
1. The inefficient memory usage in my current scheme (in which each
CGI, for example, contains its own copy of utility routines such as a
"getparent(thePath)" handler) and
2. CPU usage required by CGI-library interface requirements of the
tidier Library-based scheme.
I have a vague suspicion that the library overhead is pretty
negligible (perhaps, utterly negligible?), but I was hoping someone
might be able to shed some light and offer some observations that go
beyond that suspicion. Anyone thought this through before or done any
testing to quantify?
Since memory is pretty cheap and we are only talking about perhaps a
10 megabyte stay-open CGI memory footprint, is a library solution
worth implementing in this circumstance?
Any pros or cons to a library solution that I should be aware of? (I
have never before implemented one, although I have reviewed Bill
Cheeseman's excellent discussion at
http://www.AppleScriptSourcebook.com/tips/scriptserver.html. Thank
you, Bill!).
Will a library implementation likely survive a transfer to an OSX environment?
Grateful for any guidance or insight here,
Richard Hartman