Yes and Yes.
As far as I can see, the official network form of the data uses CRLF (this
BTW is true of POP etc).
After using Rebol for a while, we may forget that a READ converts CRLF to a
newline - which is not so good for binary data - hence the /binary
refinement of READ. This fact escaped my memory until I read the section in
the Core manul on line conversion/endings. Hence, my issue in trying to
create a set of functions useful for post data and for email which we tend
to acquire with a READ in Rebol (for email is shouldn't be a problem because
Email generally does not handle binary data - attachments and encoded in a
mail-safe form before transport).
Brett.
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, April 29, 2001 1:43 AM
Subject: [REBOL] Re: need advice on parsing image data
> We do have a CRLF 'word in REBOL, correct? That could help with parse.
>
> Are you saying that with multipart/form-data, Apache is generating POST
data
> which uses CRLF- instead of newline-terminated data?
>
> -Ryan
>
> >Me again.
> >
> >I realised a few holes in my script. And your problem has given my some
> >angst with my message-tools.r script.
> >
> >When dealing with emails we can use import-email which assumes that the
> >email has been read with a READ. The read does the line termination
> >conversion. So ok. But your post data file has shown that to deal with
> >binary data I would have to deal with CRLF line termination ( RFC1521
> >appendix G talks about this). So now I'm somewhat confused as to what I
> >should do to get my message-tools.r script handle mime-emails and
> >mime-forms.
> >
> >Argh!
> >
> >Brett.
>
> --
> To unsubscribe from this list, please send an email to
> [EMAIL PROTECTED] with "unsubscribe" in the
> subject, without the quotes.
>
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
