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> wrote:
> Hi,
>
> yesterday some folks of the team meet, to talk about WebSocket - more
> generally (HTML5) connectivity.
>
> Here is a write-up from the meeting:
>
https://gist.github.com/dd6e3c2da08830776996
>
> Feedback and comments are welcome - Please use the comment function on
> that gist!
>
> Cheers!
> Matthias
>
> --
> 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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
-- qmx