HTML-DBMS interface looks doable I did a little research on the DGI aspects and found out the following: (maybe this is a bit like reinventing the wheel, but...)
- First one has to have a little knowledge about HTML forms and CGIs - Then read "dgi.txt" and the syntax rules of "mime.cfg". For instance "inbox.dgi" is not an executable file as one may expect, but a parameter located in one of the "mime.cfg" lines (same like "image/jpg"). Search there for it and observe in what way "inbox.dgi" is associated to "insight.exe". - Then observe that, when shelling out, the necessary commands get assembled in $ROURA$.BAT (in my case located in %TEMP%\ARACHNE.TMP). This is a temporary batch file. It gets executed then deleted. - The query string location depends on how the respective line in mime.cfg looks like. If "$s" is used, the query string is passed as an argument of program call command in $ROURA$.BAT. If "$q" is used, the query string is found in $QUERY$.TMP (in the same temporary directory). A bit like "GET" and "POST" methods :). Process any dgi type form (like reply to an e-mail message) and get a snapshot of these two files. All you need is a mean to parse the query string, then pass it to the DBMS. If only there was a Perl or TCL for DOS... Regards Cristian Burneci On Wed, 1 Jan 2003 18:18:36 -0700, [EMAIL PROTECTED] wrote: <snip> > Shelling out to a program is just that - shelling OUT. The user must > still maneuver through the outside program's interface. If a DBMS looked > and operated exactly like an HTML form, then there would be no problem. > But none of them do. > My desire is to see a DBMS interface that operates from an HTML form. > When someone is taught how to use Arachne and HTML, they would > simultaneously be able to use a database. I work mostly with people who > are not familiar with electronic equipment. Lesson One is the on-off > switch. Teaching two separate (and fundamentally different) program > interfaces is counter productive to quick developmental progress. > Such a HTML-DBMS Arachne interface would open up a lot of opportunities > for all Arachne users. I've received several emails (off list) from > Arachnoids using CD-ROMs as a data server, although the data is > pre-formatted in TXT or HTM files. DB files would be even more flexible, > allowing comparisons, and-or, if-then, and a bunch of other handy > commands. >> Finally, a tip about EEK and OOK files...Read the docs folks! Plain >> as day, > Apparently not, if "folks" (plural) keep asking. Rumor has it that EEK > was originally a verbal exclamation from an early Arachne user, who was > trying to figure out the file scheme and structure. > By the way, if the instructions were in a database format, they would > have been quickly located and consolidated. Hence, fewer questions to the > list. >> OK, enough for todays lessons...Happy New Year! > Ditto. > Bob > - > ________________________________________________________________ > Sign Up for Juno Platinum Internet Access Today > Only $9.95 per month! > Visit www.juno.com -- This mail was written by user of The Arachne Browser for DOS - http://arachne.cz/ -- Arachne V1.71;UE01, NON-COMMERCIAL copy, http://arachne.cz/
