[dcc2] Other comments

[Szymon Stefanek]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 26 June 2004 13:55, myndzi wrote:
> This is getting really complex. I've been looking at the Network and
> Transport options, along with how to publish available port ranges.

The question that comes into my mind is why you need to publish a port range ?
Why should the remote party know the port ranges that you can listen on ? Or,
in the other case, why should the remote party listen on a port range choosen
by you ?

> Also notice the SID I used; I came to the conclusion recently that SID
> is mostly an unneeded field. Its only application lies in preventing
> confusion between concurrent DCC2 negotiations of the same Application
> type, and it occurs to me that it is not a very necessary thing for
> said negotiations to happen in parallel. In fact, should one fail, the
> other won't likely fare any better, with the exception of a manually
> denied connection on the part of the remote client.

But if one succeeds then the other could probably too :)
Sending two files at once (with single-file transfer) is and will remain a
common case.

> I have also noticed that it would be useful to have a specifically
> designated order to the tokens. Apptokens I believe should come after
> all the connection tokens and there should be a designated marker for
> this. Application= would be an excellent choice, since it is required
> and also would serve as an appropriate 'segue'. Apptokens only need to
> be transmitted with the Publish message, as they either provide extra
> data for use in deciding whether or not to accept the connection, or
> provide extra data for use once the connection is established.

Well.. I think that with the <name>[=<value>] pairs we can safely remove the
restriction of the token order. The restriction would make the message
parsing harder.


- --

Szymon Stefanek

- ------------------------------------------------------------------------------
- -
- - Tried anarchy, once. Found it had too many constraints.
- -
- ------------------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA3ZC4Ru+qkQYW8QERAsDxAJ9YZPUrqz90sIXeHIC/hdZ/pkFJ4wCgn+pg
cjaSaARoN6vjLkTfPEGGuRY=
=gnGr
-----END PGP SIGNATURE-----