On Fri, Apr 27, 2001 at 01:25:25PM -0500, Brandon wrote: > > B> This won't stop your node from breaking when 0.4 is released. > > > > Will anything? > > Basing it on libfreenet would make it as painless as possible as it frees > you from over-the-wire protocol issues. You'd still have to update > behaviour issues. The thing which kept 0.3 applications from ever > recovering was the over-the-wire protocol issues.
So what you're saying is that if there were a well enforced separation between the protocol message layer and the message passing logic, you could update the former without touching the latter, and you'd magically have a 0.4 compatible node? I must say that I'm a little suspicious of that theory. Is the message passing logic not a central part of the protocol? Currently reiska doesn't have a message abstraction layer, mainly because it only implements two kinds of messages -- HandshakeRequest and HandshakeReply. If 0.4 doesn't change the basic communication model between nodes (i.e. message passing and forwarding) too much, I think I'll be able to adapt reiska to the new protocol, although I probably shouldn't be talking about 0.4 compatibility without studying the 0.4 source. Besides, even libfreenet isn't the magic bullet you're looking for. If the protocol changes drastically enough, every application will have to be re-written no matter how high-level an abstraction you're providing in
