I'm looking for information about your future plans for implementing Windows
8 push notifications on the unified push server (if you've already thought
about it). I looked for topics on the mailing list but didn't find my
answers so I create this topic.
Since Windows 8 uses XML data format, what are you plans to implement it on
the UPS in the future ? Current supported platforms all use JSON, allowing
to send a notification to everyone from one command. Either you'll lose this
capability, either you'll have to "convert" JSON to XML, which is
problematic since Windows 8 has dozens of XML schemas (and some aren't
really compatible with Apple's one for example).
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/UPS-Windows-8-push-notification...
Sent from the aerogear-dev mailing list archive at Nabble.com.
Hello Aerogear dev team,
We integrated UPS into our backend server which is serving various mobile
apps. While the development and testing phase went well, my manager is
questioning me about production worthiness about Aerogear. It would be great
help if you could point me to references/success stories where UPS is being
used in production environments and scaling well in medium to high loads.
This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.
Hi Swift lovers,
In order to test if Swift could even be used to write cordova plugins and truly test the objective-c -> Swift interoperability. I’ve created a port of a very simple hello world plugin to Swfit to see if that could work.
It seems that there is only one small hurdle the Bridging-Header is not automatically added to the compiler options and the runtime libs are not there. After changing these settings by hand one can use it. I’ve asked the cordova ML if there are any solutions to these problems.
have a look that the github plugin project
want to give a heads up on the current status of Swift frameworks/static libs generation and cocoapods support. This is based on the current state of affairs, as in Xcode beta 4 (released yesterday).
Note: "Since rapid developments are taking place, will update this thread as more information becomes available and with any breaking changes"
First, let me start by making three observations:
a) quoting Apple release notes, "Xcode does not support building static libraries that include Swift code”. You can notice that in Xcode 6 when choosing “Cocoa Touch Static Library” there is no option to select “Swift” as the preferred language.
b) new in Xcode 6 is the generation of ‘dynamic’ frameworks for library targets. The reason for ‘dynamic’ linking, as explained by apple in , is to enable the new functionality in iOS 8 called ‘extensions’. Per apple quote "Frameworks work perfectly with extensions, sharing logic that can be used by both the main application, and the bundled extensions”
c) Dynamic framework for a swift library (the only option offered by Xcode) , in the current state requires the source code of the library to be build together with the app that uses it. This is due to the binary interface, which has not being finalised yet. Quoting apple blog  ("Binary Compatibility and Frameworks” section):
"While your app’s runtime compatibility is ensured, the Swift language itself will continue to evolve, and the binary interface will also change. To be safe, all components of your app should be built with the same version of Xcode and the Swift compiler to ensure that they work together.
This means that frameworks need to be managed carefully. For instance, if your project uses frameworks to share code with an embedded extension, you will want to build the frameworks, app, and extensions together. It would be dangerous to rely upon binary frameworks that use Swift — especially from third parties. As Swift changes, those frameworks will be incompatible with the rest of your app. When the binary interface stabilizes in a year or two, the Swift runtime will become part of the host OS and this limitation will no longer exist.”
What does all that gives us?
In plain form, "Distribution of the push-sdk (swift port) should be done in source form with polished documentation on how the user can add it to their own project.”
Already, looking at the various swift-libs currently in existence, that is the current approach, a well-written README.md on how the user can add the library dependency into their own projects. For example, something like the section “How to Install Library” found here 
As for cocoapods, currently no support is provided for swift projects. There is an on-going discussion on the issues list found here  on how to effectively support ‘dynamic framework’ for swift projects, and still keep backwards compatibility, but things are not yet finalised.
Let me know your thoughts / comments.
After testing and finding some small issues we are happy to announce that the 1.0.0 version of the cordova push plugin has been released. Thanks to everyone for testing and making this release happen.
AGCORDOVA-26 When app is in background notifications no longer appear on iOS
AGCORDOVA-28 Remote Notifications not enabled in generated xcode project
AGCORDOVA-27 Improve callback behaviour documentation
AGCORDOVA-10 Background push notification
Hello Swift lovers,
As discussed in our last iOS meeting , I’ve create a dedicated branch to our aerogear-ios-cookbook. All cookbook apps should be updated in Swift and uses new iOS Swift repos like aerogear-ios-http or Swift branch for aerogear-ios-push.
To keep branch name consistent I’ve named the cookbook branch ‘swift.’
As we’re starting from blank page, I’ve removed all all not yet migrated. The only apps left are linked sub-module to HelloWorld (Swift branch) and Quickstart (swift branch).
If you create new demos for next release or migrate existing demos, please target ‘swift’ branch .
We are going to release a new version of the cordova push plugin the new version 1.0.0 most important features are the updated push libraries and a fix in the content-availble flag
[AGCORDOVA-26] - When app is in background notifications no longer appear on iOS
I’ve created a 1.0.0-release  branch for your testing pleasure. If we don’t find issues we’ll perform the actual release on wednesday.