But that is using SMTP as the transport, what I wanted was to be able to use
different presentations plugably (the terms have been messed up). Since how
numbers are encoded is a property of the presentation, I didn't want any code
dealing with strings of hex chars as numbers outside the presentation classes
(ie all of that code in the implementations of Freenet.RawMessage and FieldSet,
none of it in implementations of Freenet.Message). The only way to cleanly do
this is to allow the values in the protocol to contain the information about
whether they should be read as strings or numbers or booleans.

But since this seemingly small change is such a big issue for some reason, we
will just fuck having fully pluggable presentations. There was never any direct
urgent practical reason for it, it is just a very nice feature that could have
been implemented through a very small change that I still don't understand the
motivation for making a big deal about.

On Mon, 15 May 2000, Lee Daniel Crocker wrote:
> > Forgive me if I'm misunderstanding the issue, but couldn't the gateway node
> > just blindly UU-encode the entire message into a flat text stream? Then the
> > tunneled protocol wouldn't matter.
> 
> No, you don't misunderstand at all.  That's exactly how an SMTP
> gateway ought to be written, for example.  (Or perhaps for a little
> easier debugging it could optionally put headers in plain text in
> the body and attach the trailing field in Base64.
> 
> --
> Lee Daniel Crocker <lee at piclab.com> <http://www.piclab.com/lee/>
> "All inventions or works of authorship original to me, herein and past,
> are placed irrevocably in the public domain, and may be used or modified
> for any purpose, without permission, attribution, or notification."--LDC
> 
> 
> _______________________________________________
> Freenet-dev mailing list
> Freenet-dev at lists.sourceforge.net
> http://lists.sourceforge.net/mailman/listinfo/freenet-dev
-- 
___

Oskar Sandberg
md98-osa at nada.kth.se

_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev

Reply via email to