On Tuesday, June 17, 2003, at 02:58 PM, Evan Adelman wrote:
is that really the case? if the solution involves ASP, you're probably right, you need a webserver. but php, perl, and the like are actually separate executables that you could include (1. the distribution licenses are pretty loose if i remember, and 2. all the perl executables and lib that come in the distro i have are 13MB - good enough to include on a cd)
if writing in those languages is a problem, then that's a different matter.
chiming in for no particular good,
Actually, that is pretty much what I considered as well. I only originally mentioned ASP at all because some folks use it. Here at my place it wouldn't even be considered, since we are a "PHP house" for that type of authoring.
I also don't see the speed hit as having significant impact - after all *something* will be communicating with the database. PHP is designed to do that job. It is extremely responsive with Director requests for data. No webserver or webserver technologies? mySQL will be running somewhere... locally? But PHP can't?
I'd have to agree, "if writing in those languages is a problem, then that's a different matter."
-- Troy RPSystems, Ltd. http://www.rpsystems.net
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
