[EMAIL PROTECTED] :
> I recommend you duke it out with the CGI protocol some more before giving up on this
>relatively easy protocol. Unless, of course, you have some very special protocol
>needs that CGI is not designed to handle or to handle-well. IOW, with sockets, you
>could create your own custom communication protocol. A protocol that doesn't have all
>of the un-necessary overhead of CGI, for example. You could conceivably create a
>protocol custom-made for MetaCard stacks to communicate via the Internet in their own
>native-tongue.
>
Very interesting remark IMHO.
Actually, that's what I'm planing to do. I have a few pending
projects for which the clients want a CD-ROM version + an
online version. My idea is (basically) to develop only 1 app,
on which I'll discociate the interface from the rest (core scripts
and data structures). On the CD-ROM version the interface will
be regular MC btns & flds, while the online version will
require HTML pages. The idea is to setup the small custom
protocol for communication between the core of the app and
the interface. On the CD-ROM version, this will be done by
sending messages with parameters to various handlers, and
in the online version, the same syntax will be used for
communication between the client PC (featuring the HTML
pages) and the MC app on the server.
Any thought / previous experience & comments on this ?
Thanks.
JB
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
