not every environment is Plan 9 so /env is not an option.
Arbitrary limits seem a bit, well, arbitrary ! (not that I'm complaining).
With a flat memory address space and Gbs of memory chucking a realloc in
there is not totally out of technical bounds.
Using rc in werc neutralizes OS differences to a certain degree,
obviously some things catch one out, such as this one. (and just wait
until a \0 comes along!)
In this case it might make sense to inspect Content-Length and
Content-Type and awk it with FS="&" to individual files and then inspect
their size
And then someone will want to upload Mime !
On Tue, Mar 17, 2009 at 5:26 PM, Uriel <urie...@gmail.com> wrote:
Unfortunately that doesn't work in this case, my input is HTTP post
data, which is a single line of URL-encoded text which I have to
decode into multiple parameters of arbitrary length.
writing a shell script doesn't mean you have to
write everything in the shell. why not write a
simple c program that reads stdin, decodes the
key=value arguments, and writes each "value" to
/env/form_key?
russ
