Would AeroGear.Messaging be to confusing, since this is in the gist
Current thinking is that the AeroGear Notifier will NOT be used with messaging. But
that's not really determined yet... Most-likely supporting STOMP over WebSocket would
be the way to go. Message brokers usually support STOMP (-> HortnetQ, Apache ActiveMQ,
On Dec 3, 2012, at 6:50 AM, Douglas Campos <qmx(a)qmx.me> wrote:
I like the idea of AeroGear.Notifier (guess who suggested the name?
:)) but it sounds a lot like something read-only
How about having AeroGear.Messaging, and implementing the Notifier API on top of it?
On Dec 3, 2012, at 5:46 AM, Matthias Wessendorf wrote:
> any further comments?
> On Thu, Nov 22, 2012 at 9:51 AM, Matthias Wessendorf <matzew(a)apache.org>
>> yesterday some folks of the team meet, to talk about WebSocket - more
>> generally (HTML5) connectivity.
>> Here is a write-up from the meeting:
>> Feedback and comments are welcome - Please use the comment function on
>> that gist!
>> Matthias Wessendorf
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
> Matthias Wessendorf
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> aerogear-dev mailing list
aerogear-dev mailing list