<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 28, 2013 at 12:00 AM, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">When doing selective push query, is there any overlap between mobile variant (which I understand like mobile type which contains certificates) and device type?</div>
</blockquote><div><br></div><div style>MobileVariant (or call it type) is something like "Android", or "iOS".</div><div style>deviceTypes would be iPad, iPod, iPhone, iWatch :) - or "Android Table", "Andrpid phone", android what not</div>
<div style><br></div><div style><br></div><div style>Sure.... ideally there are several variants:</div><div style><div>- iOS iPhone 5 optimised app in the app store</div><div><div>- iOS iPhone 4s optimised app in the app store</div>
</div><div><div>- iOS iPhone 3 optimised app in the app store</div></div><div><div>- iOS iPad mini optimised app in the app store</div></div><div style>etc :)</div><div style><br></div><div style>But, if there is only one variant, it's totally valid to install an iOS application (from the appstore), on an iPad and an iPhone;</div>
<div><div> <br></div></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Both aimed at defining categories. </div>
<div>
Are those categories defined and fixed in the spec or can they be extended?</div></div></blockquote><div><br></div><div><br></div><div style>I don't understand categories, here</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div>Can we do a selective push based on mobileType=mobile variant and alias=john@gmail?</div></div></blockquote><div><br></div><div style>deviceType and alias should be possible;</div><div style>It should be also possible to combine that with a variant</div>
<div style><br></div><div style>==> variant: iOS (since we have only one iOS varaint) + deviceType:iPadMini + alias: mwessendorf</div><div style><br></div><div style>I need to add that to the "Message Format" / spec</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">
On 27 May 2013 23:36, Kris Borchers <span dir="ltr"><<a href="mailto:kborcher@redhat.com" target="_blank">kborcher@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Unifying the APIs shouldn't be hard and could probably happen sooner rather than later, IMO. As far as the client goes, if you send extra info beyond the version it will just be ignored. Though, it would be better to not send the extra info to keep payload small. I guess the issue would be on the SPS side and if it can handle receiving and ignoring the extra info.<br>
<div><div><br>
On May 27, 2013, at 14:06, Daniel Passos <<a href="mailto:daniel@passos.me" target="_blank">daniel@passos.me</a>> wrote:<br>
<br>
> Very nice!<br>
> +1 to discuss later how to "unify" APIs<br>
><br>
> Matthias Wessendorf wrote:<br>
>> We /could/ (later?) try to unify the API and simply<br>
>> *IGNORE* everything besides the version, when talking<br>
>> to|SimplePush| Variant.<br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>