<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 28, 2013 at 12:56 PM, Hylke Bons <span dir="ltr">&lt;<a href="mailto:hbons@redhat.com" target="_blank">hbons@redhat.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000"><div class="im">
    <div>On 28/06/2013 11:52, Matthias
      Wessendorf wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr"><br>
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
              Thanks. So what&#39;s the use case for this? Why would you not
              want to not<br>
              use push networks specified for the main app? Also, how
              common is this?<br>
            </blockquote>
            <div><br>
            </div>
            <div>in apple, every app id (== variant) needs it&#39;s
              OWN certificate.</div>
            <div><br>
            </div>
            <div>That&#39;s why it is modeled that way</div>
            <div><br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br></div>
    This only applies to Apple APNs? I&#39;d say if there isn&#39;t a technical
    reason why you&#39;d want to this for the other networks we leave it out
    for those.<br></div></blockquote><div><br></div><div style>In Google you would use different API keys - in SimplePush it could be a different cloud provider etc </div><div style><br></div><div style><br></div><div style>
Not sure why this would be a problem</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
    <br>
    Thanks,<br>
    <br>
    Hylke<br>
    <br>
    <br>
    <br>
  </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>