On 9/20/07, Florent Daigni?re <nextgens at freenetproject.org> wrote:
> * bbackde at googlemail.com <bbackde at googlemail.com> [2007-09-20 09:00:28]:
>
> > Now, as TestDDA becames nearly mandatory (there is still an option to
> > disable the need for TestDDA), I am forced to implement it, even if I
> > have no time for it. Anyhow...
> >
> > Studying the docs about the design of TestDDA, I wonder why it was
> > implemented in a way that requires the node AND the client to maintain
> > a list of directories that were authenticated for DDA? Also it makes
> > the handling for clients more complicated because they have to trigger
> > a TestDDA.
> >
> > IMHO a better design would have been the following: Once a client
> > starts a GET or PUT, the node checks if the directory is
> > authenticated. If not, then the NODE sends a request for
> > authentication to the client. Its quite the same as the current
> > implementation, but triggered by the node, not by the client. This way
> > the client would not have to track already authenticated directories
> > per socket. The node does this anyway...
> >
> > If someone agrees that this would be a good idea, I would like to have
> > this implemented. A new option in ClientGet or ClientPut could be used
> > to tell the node that the client expects the new way to authenticate
> > for DDA. Default is to use the existing TestDDA.
>
> Once again suggestions would have been welcome when the protocol was
> designed... not now that it becomes mandatory.

Sorry that I can't follow your development cycles. I just wanted to
tell you about my idea.

>
> By the way, you can "try" to send something without TestDDA ... and if
> the node returns a ProtocolError with the DDA-reserved code then assume
> it has to be done.

I also thought about this approach (as volodya said, its not the best
one, but it fits into my design). For one who does not want to
reimplement the tracking of successfully authenticated directories,
the alternative is what thaw does (if I understand it correctly):
make a TestDDA request each time when a request is started. But I
don't want to do this, because if someone starts to get/put many
files, this would lead to many requests and the client/node have to
write/read alot of files -> big overhead.

>
> NextGen$
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFG8iM3U/Z/dHFfxtcRAnwbAKC/vdt4hSNRZufOfWEwTpWAHLiVjgCbBOeK
> 6IfCsoMXqp1NCjTIplgRqq8=
> =HLPg
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>


-- 
__________________________________________________
GnuPG key:   (0x48DBFA8A)
Keyserver:   pgpkeys.pca.dfn.de
Fingerprint:
477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A
__________________________________________________

Reply via email to