Great thing to start writing the server bits with vertx :<div><br><div>I presume you will write endpoints for register / unregister and getPushApplications functions ? <br><div><br></div><div>Do we have to discuss the format of REST services/messages or is it just a JSONfied version of the interfaces you already have ?<br>
<div><br></div><div>Vertx beeing polyglot, I assume you will write it in Groovy ;) </div><div><br></div><div><br></div><div>Seb</div><div><br><br><div class="gmail_quote">On Fri, Mar 15, 2013 at 1:55 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hijacking threads - FTW<br>
<br>
So... that feedback was great... and I am still hoping for more input<br>
on the OTHER thread...<br>
<br>
<br>
So... here is my proposal: I wait for today/monday for more feedback<br>
and I will THAN move all the ideas into a OVERALL doc - which will<br>
endup on the homepage;<br>
<br>
Also, I'll start implementing that SERVER, using vert.x - where the<br>
service/server itself is accessible via HTTP/REST (only)<br>
<br>
Thoughts?<br>
<br>
<br>
On Fri, Mar 15, 2013 at 1:47 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
><br>
><br>
><br>
> On Fri, Mar 15, 2013 at 1:28 PM, <a href="mailto:tech4j@gmail.com">tech4j@gmail.com</a> <<a href="mailto:tech4j@gmail.com">tech4j@gmail.com</a>> wrote:<br>
>><br>
>><br>
>><br>
>><br>
>> On Fri, Mar 15, 2013 at 8:25 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>>><br>
>>><br>
>>><br>
>>> On Fri, Mar 15, 2013 at 1:15 PM, <a href="mailto:tech4j@gmail.com">tech4j@gmail.com</a> <<a href="mailto:tech4j@gmail.com">tech4j@gmail.com</a>> wrote:<br>
>>>><br>
>>>> A few small comments, because I think this is looking pretty good.<br>
>>>><br>
>>>> * At first glance I like the idea of having it be a registry instead of a manager. In some ways that makes it more obvious this a logical construct.<br>
>>>><br>
>>>> * Another use case: "Other services inside of JBoss could use the push manager/registry, for example the admin console, Errai, drools, etc..."<br>
>>>> ** I.e. not just for end user apps<br>
>>><br>
>>><br>
>>><br>
>>> I think that's what I tried to address with this statement: "We want that any (JBoss/AeroGear powered) mobile application, that is backed by JBoss technology, is able to easily work with push messages. For a JBoss "backend application" it should be as simple as possible, to send messages to its different mobile clients"<br>
>>><br>
>>> ==> should not be tied to a specific backend; For instance a JSF managed bean you use the "Sender" as well - to push out messages to 'its' configured mobile apps (on the registration)<br>
>><br>
>><br>
>> ok, then yes, same page<br>
>><br>
>>><br>
>>><br>
>>>><br>
>>>><br>
>>>> * The non-native push (JS, "connected" apps, etc...) imo would/should be separate and part of AeroGear proper. I think having both functions in this one shared service would make it too complex, and hard to cover other groups use-cases. As I see it for AeroGear - we receive a msg/event/trigger that we want to send to clients. The API allows developers to say "send msg to x, y, z users/devices". AeroGear checks for any apps that are "connected" and sends a non-native push msg to those clients. AeroGear then determines who did not get a "connected" msg (that may be tricky), and uses the API your defining to send those users native push msg.<br>
>>><br>
>>><br>
>>> You mean breaking into two components?<br>
>>> - native push<br>
>>> - web based push<br>
>>><br>
>>> and an overall API on top that 'aggregates'?<br>
>><br>
>><br>
>> Yes, and yes :-)<br>
><br>
><br>
><br>
> Ah - great!<br>
><br>
> I think that is a great idea, since the "non-native" web-push is really a different case, and there are lot's of different impls - having that piece separated, makes it easier to actually implement the native push thing<br>
><br>
>><br>
>><br>
>>><br>
>>><br>
>>>><br>
>>>><br>
>>>> ** The API would have a way to set only "connected", only native, etc... as well.<br>
>>>><br>
>>>> * In the future and maybe as a POC that this can work with non-aerogear clients we could see about getting push messages setup with Christos' JBoss admin app with this. Not a priority, but an idea :-)<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Fri, Mar 15, 2013 at 6:56 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> On Fri, Mar 15, 2013 at 11:27 AM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>> On Fri, Mar 15, 2013 at 10:58 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> On Fri, Mar 15, 2013 at 10:48 AM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br>
>>>>>>>><br>
>>>>>>>> Great Job,<br>
>>>>>>>> see my comments inline.<br>
>>>>>>>><br>
>>>>>>>> On Fri, Mar 15, 2013 at 10:07 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>>>>>>>>><br>
>>>>>>>>> As discussed on the earlier theard, we have some raw APIs... Below a little summary:<br>
>>>>>>>>><br>
>>>>>>>>> We have a UnifiedPushManager(.java) defined, which is basically a registry for "push enabled" apps (PushApplication.java). Such a PushApplication is a logical construct on the backend which is allowed/enabled to send notifications to mobile clients. One example could be the "Twitter Backend" (e.g. for push notification on direct messages).<br>
>>>>>>>><br>
>>>>>>>> As you said the manager is here more a registry than a manager in the current state, maybe we should have a PushApplicationRegistry interface which has as only responsibility to hold the register state,<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> Can you gist ?<br>
>>>>>><br>
>>>>>><br>
>>>>>> Take a look at my fork <a href="https://github.com/sebastienblanc/ag-unified-push-api/tree/registry" target="_blank">https://github.com/sebastienblanc/ag-unified-push-api/tree/registry</a> ;)<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>>><br>
>>>>>>>> the implementation of the registry will connect to the chosen persistence unit (JPA/Mongo/Oracle ...).<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> Not sure I really want to that - now :) I am (for first iteration) fine to have something running, instead of being that flexible and be able to go with any existing "data source" :-)<br>
>>>>>><br>
>>>>>><br>
>>>>>> Well, for sure, for the first iteration we will provide a default implementation.<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>>><br>
>>>>>>>> This way we could have a concrete implementation of the UnifiedPushManager than can be used by different backend/customers (think DRY) , they just have to inject the needed PushApplicationRegistry implementation.<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> Not sure what exactly you mean - perhaps a gist / pseudo code is helpful here too ?<br>
>>>>>><br>
>>>>>><br>
>>>>>> Again, my fork should help you understanding <a href="https://github.com/sebastienblanc/ag-unified-push-api/tree/registry" target="_blank">https://github.com/sebastienblanc/ag-unified-push-api/tree/registry</a> but basically, it is the same as your code except I apply the delegate pattern.<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>>> Now each of the PushApplication can have a few mobile applications, that receive those push messages (e.g. the offical Twitter iOS client and the offical Twitter Android client). These "mobile apps" are represented - on the server - with the MobileApplication.java class. Usually there is only one iOS app and one Android... BUT imagine the case of a "paid/premium app" versus a free app (e.g. something like TwitterPro-iOS and Twitter-free-iOS... NOTE: there is NOTHING like that, I just made these two apps up, to explain the concept).<br>
>>>>>>>>><br>
>>>>>>>>> Of course there are several installations of the iOS(and Android...) app. Each installation is represented with theMobileApplicationInstance.java class. Each installation is registered by a "device registration service": The actual app on the device submits its token/regId (and some other infos) to a HTTP endpoint....<br>
>>>>>>>>><br>
>>>>>>>>> Now the UnifiedPushManager(.java) is the central API to register PushApps and their mobile views, including (device)registration of installations (-> MobileApplication and MobileApplicationInstance).<br>
>>>>>>>>><br>
>>>>>>>>> Any backend app, can now use the Sender API to actually send the message to these different devices/appications, from the UnifiedPushManager, assuming they have permission :-)<br>
>>>>>>>>><br>
>>>>>>>>> A simple example is here (java code for registration AND sending); Note it's a Unit test.......: <a href="https://github.com/matzew/ag-unified-push-api/blob/master/src/test/java/org/jboss/aerogear/push/UnifiedPushManagerTest.java#L41-L81" target="_blank">https://github.com/matzew/ag-unified-push-api/blob/master/src/test/java/org/jboss/aerogear/push/UnifiedPushManagerTest.java#L41-L81</a><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Maybe the Sender interface should be an attribute of the PushManager, the customer can set his Sender impl (pushManager.setSender(...) ) and the UnifiedManager act as a facade for the "sending" actions.<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> Hrm - you really think folks will write their own "Senders"? I think... if they want to add support for "Windows Mobile", they just have to extend the abstract MobileApplicationImpl and implement it's send() to talk to the Windows Push infrastrucuture<br>
>>>>>><br>
>>>>>><br>
>>>>>> Again, we will provide a default sender implementation. But I seee indedd issues, having a single senders for different platforms , hum, let me think about this ;)<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> the Sender() is an aggregate of the different mobile Application's "send()" - it will enqueue the message for the different platforms<br>
>>>>><br>
>>>>><br>
>>>>> thanks for the feedback - will check ur fork<br>
>>>>><br>
>>>>><br>
>>>>> -M<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> PERHAPS... just using interfaces was confusing - there will be concrete classes (first impl is in the TEST project (see other thread)), but the interfaces are a highlevel view of the "domain model"<br>
>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> So far, so good - but why this abstraction ????<br>
>>>>>>>>><br>
>>>>>>>>> Goal: We want that any (JBoss/AeroGear powered) mobile application, that is backed by JBoss technology, is able to easily work with push messages. For a JBoss "backend application" it should be as simple as possible, to send messages to its different mobile clients<br>
>>>>>>>>><br>
>>>>>>>>> Some Scenarios<br>
>>>>>>>>><br>
>>>>>>>>> MyWarehouseInc-backend can send messages to different "customer" groups (e.g. discounts for only iOS (or only Android) users).<br>
>>>>>>>>> MyInsuranceCorp-backend can send important "info messages" to diffenrent variants of its mobile Applications (e.g. to the MyInsuranceCustomer-APP (regardless of the OS) AND to the app for their own agents (MyInsuranceAgent-APP))<br>
>>>>>>>>> MyPublishing-Company-backend sends updates to all of its apps (free and premium - regardless of the mobile OS). Advanced content is only push to the paying customers...<br>
>>>>>>>>> A company has different backends (small apps for different tasks) - and these different backends could be able to reach all of the company's mobile apps<br>
>>>>>>>>><br>
>>>>>>>>> So... the Sender somewhat acts as a broker (for accessable apps on the 'registry' UnifiedPushManager)...<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Maybe we should define some kind of "Application" Collection, as smart/specific Java Collection implementation to be able to create easily groups of apps etc .. just a rough idea that needs to be cleaned up ;)<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> Something like that would be neat, for more advanced queries / selection etc<br>
>>>>>><br>
>>>>>><br>
>>>>>> We could have a (very) simple query language specific for Push Apps, like hibernate, we could query by example. In my fork you will see an extremely basic Query object ...<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> Thanks for the feedback!<br>
>>>>>>> -M<br>
>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> BTW... none!!!!!!! of the API names are final - happy to hear better names!!!<br>
>>>>>>>>><br>
>>>>>>>>> Please provide feedback (here and on the other thread), for missing/wrong/good items.!<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> Greetings,<br>
>>>>>>>>> Matthias<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> On Thu, Mar 14, 2013 at 6:58 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>>>>>>>>>><br>
>>>>>>>>>> here is, including device registration:<br>
>>>>>>>>>><br>
>>>>>>>>>> <a href="https://github.com/matzew/ag-unified-push-api/blob/master/src/test/java/org/jboss/aerogear/push/UnifiedPushManagerTest.java#L41-L81" target="_blank">https://github.com/matzew/ag-unified-push-api/blob/master/src/test/java/org/jboss/aerogear/push/UnifiedPushManagerTest.java#L41-L81</a><br>
>>>>>>>>>><br>
>>>>>>>>>> All hammered in java... since this is a test - most of the code will be executed, when interacting with HTTP endpoints of the thing;<br>
>>>>>>>>>><br>
>>>>>>>>>> Yes, there is no JS application in the test - but we do have an abstraction interface for it:<br>
>>>>>>>>>> <a href="https://github.com/matzew/ag-unified-push-api/blob/master/src/main/java/org/jboss/aerogear/push/application/ConnectedJavaScriptApplication.java" target="_blank">https://github.com/matzew/ag-unified-push-api/blob/master/src/main/java/org/jboss/aerogear/push/application/ConnectedJavaScriptApplication.java</a><br>
>>>>>>>>>><br>
>>>>>>>>>> Connected? Since only "online" JS clients are receiving message - there no real "push to device" for the JS world...<br>
>>>>>>>>>><br>
>>>>>>>>>> -Matthias<br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>> On Thu, Mar 14, 2013 at 3:41 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>>>>>>>>>>><br>
>>>>>>>>>>> Pushed FIRST/TEST impl + actually test case.....<br>
>>>>>>>>>>><br>
>>>>>>>>>>> <a href="https://github.com/matzew/ag-unified-push-api" target="_blank">https://github.com/matzew/ag-unified-push-api</a><br>
>>>>>>>>>>><br>
>>>>>>>>>>> YEs.... I have 'xxx'd out the KEY and certs :)<br>
>>>>>>>>>>><br>
>>>>>>>>>>><br>
>>>>>>>>>>> On Thu, Mar 14, 2013 at 11:04 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>>>>>>>>>>>><br>
>>>>>>>>>>>> My UNIT test looks (currently) like:<br>
>>>>>>>>>>>><br>
>>>>>>>>>>>> <a href="https://gist.github.com/matzew/3d7f9915afd8f6705da5" target="_blank">https://gist.github.com/matzew/3d7f9915afd8f6705da5</a><br>
>>>>>>>>>>>><br>
>>>>>>>>>>>><br>
>>>>>>>>>>>><br>
>>>>>>>>>>>> -M<br>
>>>>>>>>>>>><br>
>>>>>>>>>>>><br>
>>>>>>>>>>>><br>
>>>>>>>>>>>><br>
>>>>>>>>>>>> On Wed, Mar 13, 2013 at 11:03 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>> On Wed, Mar 13, 2013 at 10:06 PM, <a href="mailto:tech4j@gmail.com">tech4j@gmail.com</a> <<a href="mailto:tech4j@gmail.com">tech4j@gmail.com</a>> wrote:<br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>> I think this is look really good!<br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>> Here some thoughts, and/or possible additional use-cases<br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>> * How do we want to handle multiple devices for one user?<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>> Instance of 'MobileApplicationInstance'; each device has (per app) a different token;<br>
>>>>>>>>>>>>> What the apps do themselves, with multiple installs is something different.<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>> Twitter, for instance, sends the push-messages to EVERY device - but that's app specific sync<br>
>>>>>>>>>>>>> (yes, i wish there was something like IMAP, for twitter)<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>> * How do we want to handle the other side of unified push (non-native)?<br>
>>>>>>>>>>>>>> ** Might just not be there yet, but want to make sure we're still thinking the same thing :-)<br>
>>>>>>>>>>>>>> ** Would there be an additional abstraction above this for that?<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>> some sub type of 'MobileApplication' can/will cover that "mobile web" (JS client) side:<br>
>>>>>>>>>>>>> <a href="https://github.com/matzew/ag-unified-push-api/blob/master/src/main/java/org/jboss/aerogear/push/application/MobileApplication.java#L23" target="_blank">https://github.com/matzew/ag-unified-push-api/blob/master/src/main/java/org/jboss/aerogear/push/application/MobileApplication.java#L23</a><br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>> * I'm assuming there is no good way for apps to notify you when they are uninstalled?<br>
>>>>>>>>>>>>>> ** As a way of removing clutter in our tables.<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>> In apple land these are invalid tokens (see <a href="https://github.com/notnoop/java-apns/blob/master/src/main/java/com/notnoop/apns/ApnsService.java#L161" target="_blank">https://github.com/notnoop/java-apns/blob/master/src/main/java/com/notnoop/apns/ApnsService.java#L161</a>)<br>
>>>>>>>>>>>>> So, on a scheduled base they can be remove;<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>> Google has similar API (on their MulticastResult (returned by the sender))<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>> * Push filtering - I would think IDM would be very good here.<br>
>>>>>>>>>>>>>> ** Sending to roles, groups, etc...<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>> have different users (==roles), but not spec'd out<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>> ** When we store the device and app info what sub-system are you thinking?<br>
>>>>>>>>>>>>>> *** I know you were using mongo for some of the prototyping<br>
>>>>>>>>>>>>>> *** Would be possible to abstract to the IDM?<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>> yes, it should be possible (desirable) to use IDM - but does not really matter<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>> Thanks for the feedback!!!<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>> -Matthias<br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>> On Wed, Mar 13, 2013 at 12:58 PM, Douglas Campos <<a href="mailto:qmx@qmx.me">qmx@qmx.me</a>> wrote:<br>
>>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>>> On 13/03/2013, at 10:28, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>>> > ome more APIs, for some basic (initial) functionality:<br>
>>>>>>>>>>>>>>> ><br>
>>>>>>>>>>>>>>> > <a href="https://gist.github.com/matzew/c5fbc23bc97dfead46e1" target="_blank">https://gist.github.com/matzew/c5fbc23bc97dfead46e1</a><br>
>>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>>> I like the current form, but I'm sure we'll get asked about more OO(ish) APIs, like device.send(Message) - is this on the plans?<br>
>>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>>> > User/Dev enrollment can be addressed by (hopefully) reusing the ag-security.<br>
>>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>>> +1<br>
>>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>>> -- qmx<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>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>><br>
>>>>>>>>>>>>>> --<br>
>>>>>>>>>>>>>> blog: <a href="http://in.relation.to/Bloggers/Jay" target="_blank">http://in.relation.to/Bloggers/Jay</a><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>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>><br>
>>>>>>>>>>>>><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>
>>>>>>>>>>>><br>
>>>>>>>>>>>><br>
>>>>>>>>>>>><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>
>>>>>>>>>>><br>
>>>>>>>>>>><br>
>>>>>>>>>>><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>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>><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>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><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>
>>>>>>>>> _______________________________________________<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>
>>>>>>>> _______________________________________________<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>
>>>>>>><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>
>>>>>>><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>
>>>>>><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>
>>>>><br>
>>>>><br>
>>>>><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>
>>>>><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>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> blog: <a href="http://in.relation.to/Bloggers/Jay" target="_blank">http://in.relation.to/Bloggers/Jay</a><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>
>>><br>
>>><br>
>>><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>
>>><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>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>> blog: <a href="http://in.relation.to/Bloggers/Jay" target="_blank">http://in.relation.to/Bloggers/Jay</a><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>
><br>
><br>
><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>
<br>
<br>
<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>
<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></div></div></div></div>