Why the special character restriction?

Todd Olson tco2 at cornell.edu
Mon Sep 27 14:11:36 UTC 2004


Hi

At 14:34 -0600 2004-09-24, Anne Wilson wrote:
>Russ,
>
>Thanks much for the helpful response.
>
>Setting aside the issue of resources, sounds like you're saying that the
>only potentially "unsolvable" problem (without mucking with the
>protocol) is that CRLF indicates the end of a message, which could be
>erroneous in the context of binary data.
>
>Because we currently do mainly streaming transmission, for our purposes
>it might be sufficient to simply add a byte count parameter to TAKETHIS.
>  Do you think more commands would be necessary?  (Although I can imagin
>cases where we might want to do some batched transmission.)
>
>Also, are you saying that with INN I can have CR and LF in my data as
>long as they're not CRLF?  (LFCR being okay?)
>
>Anne
>

If INN were modified to handle binary data in this way
then it is likely news readers would have to be modified as well.

Regards,
Todd Olson


More information about the inn-workers mailing list