[Psi-devel] Data Transfer Proxies

[Mircea Bardac]

On Sunday 04 June 2006 03:11, Kevin Smith wrote:
> Using 'may' in JEPs means it is absolutely not a requirement, and not
> using these suggestions does not mean an implementation is at odds
> with the specificiation.

On Sunday 04 June 2006 02:47, Mircea Bardac wrote:
> -- Quote --
> Initiator Queries Server For Proxies
>
> Before attempting to initiate a bytestream, the Initiator needs to find a
> proxy. It may do so using Service Discovery as follows:
> [...]

Oh, I've thought about this too, even though JEP authors tend to capitalize 
this kind of words. Before that "may" sentence, there's:
"Before attempting to initiate a bytestream, the Initiator needs to find a 
proxy."

Well, how do you interpret "needs" under these circumstances. 
Btw, "Initiator - A Jabber Entity that wishes to establish a bytestream with 
another Entity". So, by Initiator the JEP author means the client. How dows 
Psi find a proxy?

Asking the user to look for the proxy? That's not very attractive and it's the 
main reason I brought this discussion up.

Anyhow, these days I will write a Design Document gathering the input on the 
way File Transfer should be configured - the way it should work is described 
in the JEP.


Cheers,
Mircea
/IceRAM

-- 
Psi Forums Moderator/Bug Tracker Manager
Psi Windows Installer Maintainer/ArchLinux Package Maintainer
http://mircea.bardac.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : /pipermail/psi-devel-affinix.com/attachments/20060604/9f7c5b94/attachment.pgp