On Mon, 23 Feb 2004, Miguel Howard wrote:
> Be advised, on the input side you are going to have to decode your
> parameters. If I recall correctly, that means that you are going to read
> all of stdin and then call a routine to split up the parameters and
> un-escape them.
So far I have known that I might be given a number of chars that I need
(or can) read from the input. But I don't know what "splitting up" and
"un-escaping" means ; could you give some practical examples of these?
> Just keep that in mind when you are working on the input
> side. Have a clean split between your parameter handling and your
> calculations.
>
> And on the parameter handling side, a clean spit between command line args
> vs. CGI args.
And could you give examples of these CGI args (related to POST method ;
this is all what is needed, right?)
I would better think these in as early stage as possible...
Tommi
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Jmol-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
