Re: [aerogear-dev] Notifier … What's in a name?
The more I think about this, the more I don't think there needs to be any division but
just a name change. Any suggestions on names would be appreciated. I am continuing with
Notifier for now to keep working but would like to change to something like Messager
soon.
On May 21, 2013, at 4:34 PM, Kris Borchers <kris.borchers(a)gmail.com> wrote:
Sorry, I have a thing for silly subject lines.
So as I am working on a SockJS adapter for Notifier, I have come to the realization that
Notifier is not a good name. The part of AeroGear.js does more than notify but instead
provides the ability to build adapters containing APIs for both a subscription or pub/sub
style communication system (i.e. push notifications) as well as a more complex
communication system using things like STOMP.
My first question is whether or not Notifier is trying to do to much and if so, should it
broken into 2 pieces like Notifier and Messager/Messenger (or something named like that)?
Or, should the whole thing remain as one and just be renamed.
Thoughts?
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev