Hi,
we have something like this at Sapo that has been serving us well. It
scale to a nice number of hits per sec (tested up to 10k hits/sec,
with a single server).
We can clean up the component and share it if people are interested.
Se below for more info.
On Mar 9, 2006, at 5:05 AM, Peter Saint-Andre wrote:
<img src='http://www.jabber.org/users/stpeter.png'/>
Granted there are challenges here:
1. Needs to be opt-in (no presence leaking)
we use an external component and a feature of the server that mirrors
presence information to it. It would be very simple to switch this to
registration-based or roster-based solution.
You either register with it like a MSN transport, or add a contact in
that domain.
2. User needs a way to choose icon set (if there's a choice)
You do that on the URL itself. like http://presence.site/SKIN/JID
No extra effort needed.
3. Jabber server and web server need to share information
We have two webservers in our setup, for redundancy. And they only
need to share a filesystem (NFS for example) between them. With a bit
more work, even that requirement can be dropped.
Our setup does not involve any database at all, to reduce bottlenecks.
4. Would not be dynamic (that would require an xmpp: URI)
I don't understand this, can you explain it better what you mean?
At the jabber.org domain, #3 is a bit of a pain (the web server and
jabber server are on different machines), but the challenge seems
to be
surmountable.
This would be no problem with our setup.
Best regards,
--
HIId: Pedro Melo
SMTP: [EMAIL PROTECTED]
XMPP: [EMAIL PROTECTED]
