<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 9, 2014 at 2:30 PM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br>
On 09 Jul 2014, at 14:08, Christos Vasilakis <<a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a>> wrote:<br>
<br>
> Hi all,<br>
><br>
> in order to support users that are currently want to use our Cordova push-sdk, in versions less than iOS 7 we have been discussing two options:<br>
><br>
> a) either modify the native push-sdk that currently uses iOS 7 API for its foundation networking(as of 0.9.0), to use older API that is supported both in iOS 6 and iOS 7 (but not recommended from Apple in favor of the new networking API).<br>
> b) create a branch in Cordova push-sdk plugin (e.g. ‘branch_iOS 6')that uses an older version of the native push-sdk (0.8.1) which was the last version of the native plugin that used the old networking API supporting both iOS 6 and 7.<br>
><br>
> After discussing with Eric And Matthias [1], from cordova push-plugin perspective the native API that Cordova uses hasn’t changed and option b) can be used for users that want to still support iOS 6.<br>
><br>
<br>
</div>I’ll go for the simplest. b sounds good to me.<br></blockquote><div><br></div><div>I agree that having a temporary 'iOS6 branch' is a good enough solution (with the advent of iOS8 that might be even no more relevant) </div>
<div><br></div><div>Thanks,</div><div>Matthias</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=""><br>
> Note: This branch will be there just for community's convenience of the users that for some reason want to support iOS 6 and won’t be shipped.<br>
><br>
> Thoughts?<br>
><br>
> Thanks,<br>
> Christos<br>
><br>
><br>
> [1] <a href="http://transcripts.jboss.org/channel/irc.freenode.org/%23aerogear/2014/latest.log.html#t2014-07-09T09:42:55" target="_blank">http://transcripts.jboss.org/channel/irc.freenode.org/%23aerogear/2014/latest.log.html#t2014-07-09T09:42:55</a><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
</div>> _______________________________________________<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>
<br>
<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>