L.D wrote:
>However, even if a URL exceeded the maximums allowed by DOS, it's
>immaterial; the DOS software simply needs to send the string in what
>amounts to 'packets' ... breaking it up into pieces that DOS can
>swallow, and uploading it that way until the field is completed and the
>EOL character [or other delimiter] sent.
>
>i.e. the character strings in a GIF file far exceed what you could put
>on a DOS command line; that's immaterial. It gets sent in pieces and
>saved in pieces and then processed in pieces. And we see a GIF
>picture.
Ok, I'm taking a big risk here with being seen as rude <g> - but you have
NO idea what you are talking about.
The size of the command-line is irrelevant for programs except when they
get started - they may get too few or incorrect arguments if the line is
too long. One way to solve this is to do as ex. some DJGPP programs and
send the arguments in a file.
>Where a problem can occur is if the software refuses/is unable to store
>the full length of something.
Correct, but the *programmer* chooses the size as long as there's enough
memory available (in the given memory model) - not DOS.
//Bernie
