Hi,
On Sep 3, 2008, at 8:29 PM, Justin Karneges wrote:
On Wednesday 03 September 2008 10:07:09 Artur Hefczyc wrote:
On 3 Sep 2008, at 15:13, Peter Saint-Andre wrote:
Pedro Melo wrote:
Why not make section 3 a stream feature instead?
Like:
<stream:features>
<limits xmlns='urn:xmpp:tmp:stanza-limits'>
<size>65355</size>
<rate>10</rate>
</limits>
</stream:features>
This would signal the client that the max stanza size is 65355
bytes, and the max allowed rate of stanzas per second is 10.
I like that.
/psa
+1
I like this too. The server can inform a client ahead of time what
traffic limits are going to be enforced.
This is more of a server limit though. The client still needs a
way to
negotiate its own limit, and have the server protect the client
from stanzas
larger than that limit.
ehe, Firewall XEP :).
What if your own server breaks that limit, for example, sending you
the roster? Peter would be in trouble... :)
Are we really going for the ICMP can't fragment error road?
Servers already have Max stanza size on C2S and S2S. Do we really
need more protection than that? Each time we had a error back to the
sender, we increase complexity on all the clients. And some stanzas
are really hard to break in two...
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: [EMAIL PROTECTED]
Use XMPP!
