[EMAIL PROTECTED] wrote:
> > I think there's no point in using open-proto here, since proxy
> > support would need some work below too... anyway, I'm no expert
> > here, so... :-)
>
> I just looked into root-protocol, and found 'open / 'open-proto
> were the same, so I thought it'd be a bright idea, to call
> 'open-proto, and add my changes in 'open.
Yup, but open-proto is meant to deal with proxy settings
transparently (AFAIK), otherwise you can just call
system/words/open for the TCP connection; in your case, you need
to open a listen port after the connection, and I don't know what
happens there if you're under SOCKS or something like that... so
perhaps it wouldn't work under a proxy anyway...
> > I think you can return answer here too (even if returning data
> > from insert is not consistent with other protocols)
>
> Was thinking about this, too. Well actually write may behave like
> read in freenet protocol (right now), when trying to add a key,
> that's already in the system ...
I think the "standard" is to return data in the subsequent copy;
that is, insert writes only, and copy reads only. BTW, if you want
to know how to handle OPEN's refinements (like /read, /lines,
/allow etc.), let me know. I did figure out how it works without
needing to bother Jeff with questions... ;-)
Ciao,
/Gabriele./
o--------------------) .-^-. (----------------------------------o
| Gabriele Santilli / /_/_\_\ \ Amiga Group Italia --- L'Aquila |
| GIESSE on IRC \ \-\_/-/ / http://www.amyresource.it/AGI/ |
o--------------------) `-v-' (----------------------------------o
