hmm, going to have to get some tutorials on the various client libs folks have settled on (and poke Nathan to demo the ones we use) :)
On Wed, Jun 25, 2008 at 4:26 PM, Steve Ivy <[EMAIL PROTECTED]> wrote: > All, > > Thanks for the great info! Gives me some stuff to think about. I > hadn't seen JSJaC before, I'll definitely be looking at that further. > > --Steve > > On Wed, Jun 25, 2008 at 11:17 AM, Daniel Mills <[EMAIL PROTECTED]> wrote: >> We're not exposing XMPP to users directly. Currently, we use it only to >> implement bookmarks sharing notifications between accounts. The >> notifications are processed and displayed along with other Weave >> notifications. We hope to use XMPP to implement the actual data >> distribution, though (we do that over WebDAV right now). >> We wrote our own XMPP stack to get started, but we're considering to switch >> to JSJaC in the future. >> Dan >> >> On Jun 25, 2008, at 11:04 AM, Mickaël Rémond wrote: >> >> Interesting. Are you using any special mechanism or direct messaging to the >> users ? >> Le 25 juin 08 à 19:58, Aza a écrit : >> >> In Mozilla Labs, we are using XMPP in Weave to push around real-time updates >> to the stuff you want to sync between browsers/mobile/etc. >> >> -- aza | ɐzɐ -- >> >> On Wed, Jun 25, 2008 at 10:21 AM, Mickaël Rémond >> <[EMAIL PROTECTED]> wrote: >>> >>> Hello, >>> To complete on this: >>> - we have worked on lots of big non chat / IM oriented project. Some of >>> them are in the gaming world (from betting to more casual games). >>> - quite a large part of our customer base is building various types of >>> social network. If you search a bit I am sure you will find some (maybe not >>> easily the biggest ones however). >>> We have developed our pluggable and extensible pubsub API especially for >>> this type of needs. >>> This is something I will talk about in London on friday: >>> >>> http://www.process-one.net/en/blogs/article/erlang_exchange_london_uk_june_27th/ >>> Le 25 juin 08 à 19:05, Blaine Cook a écrit : >>> >>> * Obviously Twitter is one of the better-known examples, send millions of >>> messages a day, and have a [proper] PubSub endpoint that hasn't gone live. >>> * iminlikewithyou uses XMPP to run their games (possibly other stuff) >>> * In a conversation with Alex @ twitter, he mentioned that some "big >>> media" online gaming company is using XMPP (specifically Openfire) to handle >>> all of their chat stuff. >>> >>> * I'm working with three separate (two high-profile) sites that are >>> interested in adding XMPP support, espeically the PubSub angle. >>> >>> I think the challenge is finding applications of XMPP where the developers >>> have opened up access to outside developers. Thankfully, I think that's the >>> shift we're seeing, and many of the examples on this thread are along those >>> lines. >>> b. >>> >>> On Wed, Jun 25, 2008 at 8:01 AM, Steve Ivy <[EMAIL PROTECTED]> wrote: >>>> >>>> There's been a long discussion recently (some of which happened on >>>> this list) about open messaging between websites and between users on >>>> those websites, based somewhat on the current social network friends >>>> messaging model. I think there's a general consensus that XMPP can and >>>> should play an important role in this idea of an open, distributed, >>>> near-real-time network of websites, but I also think that there is >>>> disagreement on what the transition from xmpp's real-time network to >>>> the web's non-real-time, non-persistent network looks like. >>>> >>>> In the interest in understanding different ways that XMPP can be >>>> used/built on, I'm wondering if anyone has some examples of a >>>> real-world XMPP deployment for non-IM purposes? Perhaps something >>>> based on PubSub? >>>> >>>> Thanks, >>>> >>>> --Steve >>>> >>>> -- >>>> Steve Ivy >>>> http://redmonk.net // http://diso-project.org >>>> This email is: [ ] bloggable [x] ask first [ ] private >>> >>> >>> -- >>> Mickaël Rémond >>> http://www.process-one.net/ >> >> -- >> Mickaël Rémond >> http://www.process-one.net/ >> >> >> >> > > > > -- > Steve Ivy > http://redmonk.net // http://diso-project.org > This email is: [ ] bloggable [x] ask first [ ] private > -- --- Bear [EMAIL PROTECTED] (work) [EMAIL PROTECTED] (jabber & email) http://code-bear.com/bearlog (weblog) PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
