[ticker-dev] Ticker logging

[Phillips, Matthew]

> > The second point is relevant to me (being just such a 
> fascist) but I'm 
> > guessing that you are going to say "let presence in" to which I say 
> > "not until the amount of traffic drops significantly"
> 
> This is a bit of a concern ... it shouldn't be so much 
> traffic that people are forced to block it because of the 
> volume (especially given the limited size of the current user 
> community).

If you suscribe to presence notifications it can look like a lot of traffic, especially if you hit a burst (eg when someone logs in and makes a request for a lot of groups/buddies). Plus Martin's eTiks is still responding to *every* request ')

[It's made a lot messier at the moment by the issue I alluded to on ticker earlier where the Sticker 3.0 clients are erroneously counting certain update ntfns as globally visible and thus not emitting a periodic keepalive within a 5-minute window, causing the 3.1 clients (which have an optimisation of their presence subscription) to periodically re-request their info. While the de-centralised, stateless nature of the protocol is generally mostly a really good thing, this is one of those bad aspects: an implementation error in the clients is much harder to fix.]

As a quick test, I just ran ec with a presence sub of "require(Presence-Protocol)" over 10 minutes, output to a file, which has come to 254KB. Assuming the textual dump from ec roughly translates to the amount of net traffic (??), that's an average of 0.42KB/sec or 35MB/day. This is a very rough estimate, but it doesn't seem ridiculously high if you've got a corporate-sized pipe?

Cheers,

Matthew.