<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>Sent from my iPhone</div><div><br>On May 31, 2013, at 12:24 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br><br></div><blockquote type="cite"><div>somehow the device needs to say: "I belong to android variant"<div><br></div><div>besides the @Id /PK, we can have a second field / column that represents:</div><div>* PushAppID</div><div>* VariantID</div><div><br></div></div></blockquote><div>Yup. Having these would solve that</div><div><br></div><br><blockquote type="cite"><div><div>
</div><div><br></div><div>Was that your question? <span></span><br><br>On Friday, May 31, 2013, Lucas Holmquist wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">something that i was thinking about after doing some examples is that i'm not sure how i feel about using the PK's of each table as the identifier to register/broadcast clients.<div>
<br></div><div>We are sort of giving meaning to data that really shouldn't have meaning. it should really only be used to identify the row. It might be better to have another key on each table/object that is the identifier.</div>
<div><br></div><div>So in one of the examples i did, the app on the device will register the device with the push server, but i needed to also include the id of the variant instance</div><div><br></div><div>i guess i'm thinking if someone migrates their database, these keys could get messed up.</div>
<div><br></div><div><br></div><div>wdyt?</div><div><br></div><div><br><div><div>On May 28, 2013, at 2:53 AM, Matthias Wessendorf <<a>matzew@apache.org</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr"><br>
<div><br><br><div>On Tue, May 28, 2013 at 8:51 AM, Corinne Krych <span dir="ltr"><<a>corinnekrych@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">in selective push is:<br><div><span style="font-family:arial,sans-serif">==> variant: iOS </span><span style="font-family:arial,sans-serif"> + alias: mwessendorf</span><font face="arial, sans-serif"><br>
</font></div>a valid criteria too?<br></div></blockquote><div><br></div><div><br></div><div>yes. let me update the related doc(s)</div><div> </div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"></div><div><div><div><br><br><div>On 28 May 2013 08:51, Corinne Krych <span dir="ltr"><<a>corinnekrych@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br></div><div><br><br><div>
On 28 May 2013 08:48, Matthias Wessendorf <span dir="ltr"><<a>matzew@apache.org</a>></span> wrote:<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">TYPO:<div><font face="arial, sans-serif">==> variant: iOS (since a PushAPP _might_ have only one iOS variant) + deviceType:iPadMini + alias: mwessendorf</font><br>
</div><div><font face="arial, sans-serif">or</font></div>
<div><span style="font-family:arial,sans-serif">==> variant: iOS (since a PushAPP _might_ have only one iOS variant</span><span style="font-family:arial,sans-serif">) + deviceType:iPhone + alias: mwessendorf</span><font face="arial, sans-serif"><br>
</font></div><div><span style="font-family:arial,sans-serif"><br></span></div><div><span style="font-family:arial,sans-serif"><br></span></div><div><br></div></div><div><div>
<br><br><div>
On Tue, May 28, 2013 at 8:43 AM, Matthias Wessendorf <span dir="ltr"><<a>matzew@apache.org</a>></span> wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br><div><br><br><div><div>On Tue, May 28, 2013 at 12:00 AM, Corinne Krych <span dir="ltr"><<a>corinnekrych@gmail.com</a>></span> wrote:<br>
<blockquote 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><div>MobileVariant (or call it type) is something like "Android", or "iOS".</div><div>deviceTypes would be iPad, iPod, iPhone, iWatch :) - or "Android Table", "Andrpid phone", android what not</div>
<div><br></div><div><br></div><div>Sure.... ideally there are several variants:</div><div><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>- iOS iPhone 3 optimised app in the app store</div><div>- iOS iPad mini optimised app in the app store</div><div>etc :)</div><div><br></div><div>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> <br></div></div><div><blockquote 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><div>I don't understand categories, here</div><div><div> </div><blockquote 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">Can we do a selective push based on mobileType=mobile variant and alias=john@gmail?</div></blockquote><div><br></div></div></div></div></div></blockquote></div></div></div></blockquote></div></div></blockquote>
</div></div></div></div></blockquote></div></div></div></blockquote></div></div></div></blockquote></div><br><br>-- <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><br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>aerogear-dev mailing list</span><br><span><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></span></div></blockquote></body></html>