Actually this thread is in regards to
"Requirements of a server-side companion for
DynAPI" This would (or should) encompass all the server-side stuff we could
want to do in conjunction with DynAPI Such as file i/o CROSS-PLATFORM database
handling,Useful, as I may be
moving my site (www.allthewhile.com)
to a new server , and god knows what platform that will run
on..I DON'T want to re-write ALL
of the database code for ODBC, or perl, or whatever, because I can no longer
use my activeX dll.
That's the beauty of PERL (DBI/DBD),
I have it running on my NT at Home, On Solaris and Redhat here at work and
it supports a bunch of other platforms.
My point
exactly.
You
completelyt massacured my beutiful doc.. :-(
What the heck are you using to encode
HTML, because Netscape composer really don't like it very much (is this
better?)
Outlook Express.. I'm
switching in the next couple of day tho..
Anyone have any
suggestions?
I also have some ideas for Discipline
specifically stuff, namely Mapping and GIS functions.
WEll, let's hear them
then!! :-)
bobb
Doug
