Hi Martin, Thanks for sharing Beacon push. There are a couple of other such services as well. I evaluated them before opting for Channel API for Review19<http://www.review19.com> .
Reason being, the list of people to broadcast to is dynamic. For my app, there aren't fixed "rooms" or "groups" but the broadcast recipients changes frequently. Channel API doesn't impose any rules, and forces you to persist client state on the server. This initially "feels" wrong but can be a blessing in disguise as you optimize the logic to decide the broadcast recipients. I'm not saying Beacon Push and similar services are "bad". They just didn't work as well as Channel API for my use case. - Sri On Thu, Sep 1, 2011 at 8:21 AM, Martin Ceperley <mar...@ceperley.com> wrote: > Richard, a good alternative to the Channel API is Beacon Push ( > http://beaconpush.com/) we have been using it and it's dead simple and > works flawlessly. It supports broadcast messaging (with channel API does not > out of the box) as well as per-user messaging. Also extremely affordable, 3 > million messages for $3.29. > > -Martin > > On Aug 31, 2011, at 10:33 PM, Richard Arrano wrote: > > I'll be leaving if some of the prices aren't tweaked, particularly the > channels. I was banking on being able to use a large amount of > channels, likely in the thousands per day. I did a double take when I > realized the new price was per hundred rather than per thousand, > particularly when channels expire after two hours and need to be re- > created. Does anyone have a good alternative to the Channel API using > Amazon's solutions? > > -Richard > > On Aug 31, 6:05 pm, "Raymond C." <windz...@gmail.com> wrote: > > I am not asking who is not happy with the new pricing (virtually most of > GAE > > users). > > > I am just asking who is FORCED to leave GAE because you cannot afford to > > keep running on GAE under the new pricing model. Please (if possible) > state > > the monthly price change as well. > > > And what options you are considering? > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Srirangan | About <http://srirangan.net/about> Blog<http://srirangan.net> GitHub <https://github.com/Srirangan> LinkedIn<http://www.linkedin.com/in/srirangan> Twitter <http://twitter.com/srirangan> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
