Hi Nick, Interesting idea - I'd not really looked at PubSubHubbub before. Sadly I don't think it's the right fit for this project - they're desktop apps, and they're often behind a firewall, so getting an external server to initiate a connection isn't going to be practical.
So back to XMPP, there are two things putting me off creating separate accounts: * Speed - won't announcing to a single account be much faster to process? * Sign-up - more importantly, I don't really want people to have to create a new account to use my software. There's no need from my end - I want to give this information away freely. Using a single, shared, read-only* account would avoid bothering the user. Any thoughts? From what you've said, it sounds like it's worth trying a pilot scheme, at least. :-) Thanks, Kris * Read-only in the sense that if anyone does send a message from the client account, no-one's listening, so it doesn't matter. On Oct 13, 12:09 pm, "Nick Johnson (Google)" <[email protected]> wrote: > Hi Kris, > Have you considered using PubSubHubbub? If your 'clients' are other servers, > this is exactly what it's designed for. If your clients are, eg, desktop > apps, the XMPP solution is probably a good one, though realistically you > probably want each client to have a separate account, and notify them > individually. > > -Nick Johnson > > -Nick Johnson > > > > > > On Mon, Oct 12, 2009 at 9:03 PM, Kris <[email protected]> wrote: > > > Can I bounce an idea off anyone who's interested? I'm looking for an > > efficient way to get realtime updates to a large-ish number of client > > apps, and I'm wondering if using App Engine+Google's Talk servers > > might be the way to do it. > > > I need to get timely messages to 100-5000 thousand clients, with > > reasonable (99%?) reliability. I know I can do this with Google Talk > > at a very small scale - if someone IMs me I'll get the message through > > Gmail on one computer, iChat on another and Google Talk on my iPhone, > > all at the same time. But that's just 3 clients on the same account. > > Could this work at scale? > > > Let's say I create an account - [email protected] - and > > have my all my client apps connect as that user. They're all coded to > > listen for updates from their buddy - [email protected] - > > which is part of my App Engine project. As far as I understand, > > they'll all hear everything the server is announcing, roughly at the > > same time. > > > Does anyone know that this would/wouldn't work? And if it would work, > > does anyone know the billing implications? I'd rather the App Engine > > team billed me for 5000 messages and were happy to do so, than billed > > me for one but felt I was abusing the system. > > > (Sorry - I realise this may be more of a Google Talk question than an > > App Engine question. If anyone wants to point me to a low-level GTalk > > forum instead, please do!) > > -- > Nick Johnson, Developer Programs Engineer, App Engine > Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: > 368047 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
