On Wed, Jul 10, 2013 at 12:00 PM, Sebastien Blanc <scm.blanc@gmail.com> wrote:
On Wed, Jul 10, 2013 at 11:51 AM, Matthias Wessendorf <matzew@apache.org> wrote:
On Wed, Jul 10, 2013 at 11:47 AM, Sebastien Blanc <scm.blanc@gmail.com> wrote:
You mean adding this to the Java Sender API ?I thought adding it to the SERVER, but yeah the Java Client needs to reflect that as well :-)I'm okay with it but we just have to keep in mind that the backend app using the sender should be totally agnostic to who it send messages to (And the backend app should not know the variant ids, only the push app id, so .... ) maybe using another terminology ?Not sure I agree.Sure it is not about agreeing or disagreeing here ;) but we should discuss this. Maybe the backend could query the push server to retrive the available variants ?Interesting point - but that's a different discussion :)Not sure I want the business backend to query the PushServer, asking for variants .... ( also a right issue).Even so... if that hook would be added to the server...., we would still need the "variants" : {arrayOfVariantIDs} on the REST endpoint, and a reflection of that, on the JAva Sender, right ?
-MatthiasA marketing backend could have a special "coupon" for Tablet users. Again, it's up the business logic :-)-MatthiasOn Wed, Jul 10, 2013 at 11:34 AM, Matthias Wessendorf <matzew@apache.org> wrote:
_______________________________________________Hi,For adding support to "select" some variants (e.g. "Android Tablet optimized variant" _and_ "iPad mini variant" _and_ "SimplePush variant"), when sending messages, I'd like to update the Selective Sender API and add a new field:"variants" : {arrayOfVariantIDs}IMO the broadcast should NOT have such an option, since it broadcasts to everything. At least that's my understanding of it.Any thoughts?--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev