Push notifications

[Rambabu]

Hi,

Is there any way to implement push notifications for rabbitmq clients?

Thanks

[Michael Klishin]

On 3 November 2015 at 07:41:39, Rambabu (rambabu...@gmail.com) wrote:
> Is there any way to implement push notifications for rabbitmq
> clients?

Messaging protocols we support already have some operations that are server-sent:
for example, in AMQP 0-9-1 they are basic.deliver, basic.return, basic.cancel, connection.[un]blocked.

What specifically are you looking to accomplish? 
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Michael Klishin]

On 3 November 2015 at 07:41:39, Rambabu (rambabu...@gmail.com) wrote:

> Is there any way to implement push notifications for rabbitmq
> clients?

What specifically are you looking for? There are multiple protocol methods
that are server-sent (in AMQP 0-9-1, but this is generally true for the messaging
protocols we support):

 * basic.deliver
 * basic.return
 * basic.cancel
 * connection.[un]blocked

So what exactly is missing? 

[Rambabu]

Hi MK,

Sorry to misleading you. Actually my intension is to implement Apple and Android push notifications(For Android and iPhone devices)


Thanks

[Michael Klishin]

On 3 November 2015 at 08:36:56, Rambabu (rambabu...@gmail.com) wrote:
> Actually my intension is to implement Apple and Android push
> notifications(For Android and iPhone devices)

OK, so you want to propagate messages to iOS and Android devices as
push notifications.

We don't have immediate plans to add something like this. In fact, I'm not sure
how much value there would be: what messages should be propagated and what rates
are reasonable varies from system to system, so we can't make assumptions about it.

At the same time, developing a tiny service that consumes messages from RabbitMQ
and propagates them to iOS and Android push notification services shouldn't be too time consuming
and would give you full control over what is propagated and how.

That said, if you have ideas about what such a notifications plugin would do and what
its value proposition would be, let us know. 

[Rambabu]

Hi MK,

For apple or android push notifications we need to know client connectivity loss. For that i would like to write tiny client based on rabbitmq-event-exchange. But with that we are unable to map client with connection(In other thread i was discussed same case).

Is there any way to know which client got closed/connected?

At lease if we know channel name also at client side is fine.

Thanks

[Michael Klishin]

On 3 November 2015 at 12:12:44, Rambabu (rambabu...@gmail.com) wrote:
> For apple or android push notifications we need to know client
> connectivity loss. For that i would like to write tiny client
> based on rabbitmq-event-exchange. But with that we are unable
> to map client with connection(In other thread i was discussed
> same case).
>
> Is there any way to know which client got closed/connected?

Certain client libraries provide an easy way to detect connection loss,
e.g. see shutdown handlers in the Java one.

librabbitmq-c can be a lot trickier.

[Alan Antonuk]

Getting push notifications to work reliably on a mobile device is actually quite difficult, and I'd argue while AMQP does have a heartbeat feature, its not a protocol designed around doing push notification over unreliable network links well (its designed to work well in WAN environments).

Depending on your requirements you might be better served by using the native push notification service like: GCM.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send an email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.