<div dir="ltr">I like <span style="font-family:arial,sans-serif;font-size:13px">AeroDoc</span><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div style><span style="font-family:arial,sans-serif;font-size:13px">-Matthias</span></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 1, 2013 at 11:10 PM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">BroDoctor? AeroDoc? HealthBoard? Pushpital? Doppler<br>
(<a href="http://disney.wikia.com/wiki/Dr._Delbert_Doppler" target="_blank">http://disney.wikia.com/wiki/Dr._Delbert_Doppler</a>)? Mc McStuffins<br>
(<a href="http://www.youtube.com/watch?v=UwzgGFPpHCA" target="_blank">http://www.youtube.com/watch?v=UwzgGFPpHCA</a> - In this situation we have<br>
a video).<br>
<br>
/me runs<br>
<div class="im"><br>
Jay Balunas wrote:<br>
> Some bad ones and good ones pop into my head, I'll leave you to decide<br>
> which ;-)<br>
><br>
> DrLead<br>
> LeadFinder<br>
> AGLead<br>
> LeadsAG<br>
> aerogear-push-example<br>
> urLeads<br>
><br>
><br>
> On Jul 1, 2013, at 10:33 AM, Matthias Wessendorf wrote:<br>
><br>
>> As said somewhere (mailing list thread), IRC, not only the repo would<br>
>> need a rename, the project itself as well.<br>
>><br>
>><br>
>> So, feel free to suggested new names for this "topic demo"<br>
>><br>
>> -Matthias<br>
>><br>
>><br>
>> On Fri, Jun 28, 2013 at 10:55 PM, Jay Balunas <<a href="mailto:jbalunas@redhat.com">jbalunas@redhat.com</a><br>
</div><div><div class="h5">>> <mailto:<a href="mailto:jbalunas@redhat.com">jbalunas@redhat.com</a>>> wrote:<br>
>><br>
>><br>
>> On Jun 28, 2013, at 2:54 AM, Corinne Krych wrote:<br>
>><br>
>> > According to that thread:<br>
>> ><br>
>> <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-demo-planning-td3569.html" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-demo-planning-td3569.html</a><br>
>> ><br>
>> > it's a topic example to be more exact :)<br>
>> ><br>
>> > * Topic examples: I believe these should have a similar<br>
>> requirement as the showcase example. The point of the topic<br>
>> example is to cover a specific topic, not specific individual clients.<br>
>> ><br>
>> > Should we have a naming convention?<br>
>> ><br>
>> > I suggest something like:<br>
>> ><br>
>> > aerogear-topic-example-prodoctor-*<br>
>><br>
>> I think we could likely just go with:<br>
>><br>
>> aerogear-prodoctor-* as I don't think the distinction between<br>
>> example files will mean much to most people. The README should<br>
>> address the difference imo though.<br>
>><br>
>> This also leads to the repo planning thread we discussed creating.<br>
>> Lets kick that off early next week as I think for the most part we<br>
>> are in general agreement with the "example planning thread".<br>
>><br>
>> > aerogear-topic-example-todo-*<br>
>> ><br>
>> > By the way I put TODO "demo" in the same category. Do you all agree?<br>
>> > Given we find another name for ProDoctor, maybe TensioLeads or<br>
>> just Leads because the business focus could be anything else.<br>
>> ><br>
>> > wdyt?<br>
>> ><br>
>> > ++<br>
>> > Corinne<br>
>> ><br>
>> > On Jun 28, 2013, at 7:57 AM, Matthias Wessendorf<br>
</div></div><div class="im">>> <<a href="mailto:matzew@apache.org">matzew@apache.org</a> <mailto:<a href="mailto:matzew@apache.org">matzew@apache.org</a>>> wrote:<br>
>> ><br>
>> >> On Thu, Jun 27, 2013 at 11:11 PM, Summers Pittman<br>
</div><div><div class="h5">>> <<a href="mailto:supittma@redhat.com">supittma@redhat.com</a> <mailto:<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>>> wrote:<br>
>> >>> On 06/27/2013 03:23 PM, Corinne Krych wrote:<br>
>> >>>> Hello all,<br>
>> >>>><br>
>> >>>> Before renaming, I suggest we choose which category we want<br>
>> to tag ProDoctor. From Jay proposal:<br>
>> >>>> - showcase demo<br>
>> >>>> - topics demos<br>
>> >>>> - quickstart<br>
>> >>>> - one off examples.<br>
>> >>>><br>
>> >>>> Given those categories, I think ProDoctor is between topics<br>
>> demos and a first draft for showcase demo.<br>
>> >>> +1 to it being a topics demo.<br>
>> >><br>
>> >> I agree on topic demo.<br>
>> >><br>
>> >><br>
>> >><br>
>> >>>><br>
>> >>>> Do we want to keep the topics demos category ? As Pete Muir<br>
>> pointed out, does it make sense?<br>
>> >>>><br>
>> >>>> or do we prefer to enhance our quick start/tutorials with<br>
>> different scenarios? Maybe working on the recipes/cookbook<br>
>> approach as defined by passos.<br>
>> >>>><br>
>> >>>> We could recycle ProDoctor into several quickstarts (simplify<br>
>> code) and make difference cases: selective push, broadcast etc…<br>
>> >>>> We could also reuse some material for showcase demo and off<br>
>> course make it blogpost.<br>
>> >>>><br>
>> >>>> Several options. Depending on the choice we then get a name.<br>
>> >>>> Just wondering which category does the TODO app falls in?<br>
>> >>>><br>
>> >>>> ++<br>
>> >>>> Corinne<br>
>> >>>><br>
>> >>>><br>
>> >>>> On Jun 27, 2013, at 7:08 PM, Matthias Wessendorf<br>
</div></div><div class="im">>> <<a href="mailto:matzew@apache.org">matzew@apache.org</a> <mailto:<a href="mailto:matzew@apache.org">matzew@apache.org</a>>> wrote:<br>
>> >>>><br>
>> >>>>> On Thu, Jun 27, 2013 at 7:01 PM, Kris Borchers<br>
</div><div class="im">>> <<a href="mailto:kris@redhat.com">kris@redhat.com</a> <mailto:<a href="mailto:kris@redhat.com">kris@redhat.com</a>>> wrote:<br>
>> >>>>>> On Jun 27, 2013, at 11:57 AM, Matthias Wessendorf<br>
</div><div class="im">>> <<a href="mailto:matzew@apache.org">matzew@apache.org</a> <mailto:<a href="mailto:matzew@apache.org">matzew@apache.org</a>>> wrote:<br>
>> >>>>>><br>
>> >>>>>>> Any more thoughts on this ?<br>
>> >>>>>>><br>
>> >>>>>>> Looks like right now the favorite is:<br>
>> >>>>>>> aerogear-prodoctor-**<br>
>> >>>>>> Definitely thought we were changing the name so probably<br>
>> not good to name the repo that.<br>
>> >>>>> exactly :)<br>
>> >>>>><br>
>> >>>>> name (and repo) needs to be changed :)<br>
>> >>>>><br>
>> >>>>> Any "proposals" ?<br>
>> >>>>><br>
>> >>>>>>> Perhaps we can find something "better" for the "prodoctor"...<br>
>> >>>>>>><br>
>> >>>>>>> On Tue, Jun 25, 2013 at 11:40 AM, Matthias Wessendorf<br>
</div><div class="im">>> <<a href="mailto:matzew@apache.org">matzew@apache.org</a> <mailto:<a href="mailto:matzew@apache.org">matzew@apache.org</a>>> wrote:<br>
>> >>>>>>>><br>
>> >>>>>>>><br>
>> >>>>>>>> On Tue, Jun 25, 2013 at 10:52 AM, Corinne Krych<br>
</div>>> <<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a> <mailto:<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a>>><br>
<div class="im">>> >>>>>>>> wrote:<br>
>> >>>>>>>>> It's depend what we want to do with it.<br>
>> >>>>>>>>><br>
>> >>>>>>>>> If it's to demo Push feature only I would suggest:<br>
>> >>>>>>>>> aerogear-push-demo-backend/ios/web/android<br>
>> >>>>>>>>><br>
>> >>>>>>>>> If we want to demo more features we could call it simply<br>
>> >>>>>>>>> aerogear-prodoctor-…<br>
>> >>>>>>>><br>
>> >>>>>>>> yeah, works for me too. It's simple :)<br>
>> >>>>>>>><br>
>> >>>>>>>>><br>
>> >>>>>>>>> ++<br>
>> >>>>>>>>> Corinne<br>
>> >>>>>>>>><br>
>> >>>>>>>>> On Jun 25, 2013, at 9:54 AM, Matthias Wessendorf<br>
</div>>> <<a href="mailto:matzew@apache.org">matzew@apache.org</a> <mailto:<a href="mailto:matzew@apache.org">matzew@apache.org</a>>><br>
<div class="im">>> >>>>>>>>> wrote:<br>
>> >>>>>>>>><br>
>> >>>>>>>>> Hi,<br>
>> >>>>>>>>><br>
>> >>>>>>>>><br>
>> >>>>>>>>> this is not really a quick start :) So I am asking for<br>
>> new names.<br>
>> >>>>>>>>><br>
>> >>>>>>>>> Once have have decided on "better" repo names for this,<br>
>> I'll create a JIRA<br>
>> >>>>>>>>> so that the repos will be renamed to better reflect what<br>
>> they actually<br>
>> >>>>>>>>> are...<br>
>> >>>>>>>>><br>
>> >>>>>>>>><br>
>> >>>>>>>>> Thoughts?<br>
>> >>>>>>>>><br>
>> >>>>>>>>> -Matthias<br>
>> >>>>>>>>><br>
>> >>>>>>>>><br>
>> >>>>>>>>><br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> On Jun 11, 2013, at 10:45 AM, Sebastien Blanc<br>
</div>>> <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a> <mailto:<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>>><br>
<div><div class="h5">>> >>>>>>>>>> wrote:<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> Hey !<br>
>> >>>>>>>>>> We would like to provide, in a quite short delay<br>
>> (coming 2 weeks) a demo<br>
>> >>>>>>>>>> showing all the different bits of the "push" world ,<br>
>> meaning :<br>
>> >>>>>>>>>> client | push server | JEE Backend App<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> We already have the push server<br>
>> (aerogear-unified-push-server) : so we<br>
>> >>>>>>>>>> need a client (iOS and maybe also Android) and a simple<br>
>> JEE backend<br>
>> >>>>>>>>>> application. The backend app will mostly be scaffolded<br>
>> and will use the<br>
>> >>>>>>>>>> aerogear-unified-push-java-client to send messages to<br>
>> the Push Server.<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> Then of course, we need to think about an idea of the<br>
>> application itself.<br>
>> >>>>>>>>>> It needs to stay really simple, show how we can send<br>
>> selectively and should<br>
>> >>>>>>>>>> be a bit "business" related.<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> So, I came up with an idea this morning that we can<br>
>> discuss here, of<br>
>> >>>>>>>>>> course if you have any other idea don't hesitate to<br>
>> share it.<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> Push Demo<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> Introduction<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> Prodoctor is a company in the health care industry,<br>
>> selling a<br>
>> >>>>>>>>>> revolutionary tensiometer. Their clients are doctors.<br>
>> Prodoctor has several<br>
>> >>>>>>>>>> sales agents all over the United States. At the<br>
>> headquarters, they have<br>
>> >>>>>>>>>> their "first line" sales department doing cold calls<br>
>> all along the day. As<br>
>> >>>>>>>>>> soon they have a concrete lead, they use their<br>
>> Prodoctor Admin app to filter<br>
>> >>>>>>>>>> out available sales Agents available in the lead area.<br>
>> They can then send<br>
>> >>>>>>>>>> them a push notification.<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> The sales agent receives the notification on their<br>
>> mobile device that a<br>
>> >>>>>>>>>> new lead is available. The agent will handle the lead<br>
>> by "accepting" the<br>
>> >>>>>>>>>> notification informing the other agents that the lead<br>
>> has been processed.<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> The client app<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> The client consist of a list of leads : a lead can be<br>
>> "open" or "in<br>
>> >>>>>>>>>> process", leads "in process" of other sales are not<br>
>> visible.<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> optional : when the client tap a lead it appears on a map<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> The client has a status that he can set: STANDBY |<br>
>> WITH_CLIENT |PTO<br>
>> >>>>>>>>>> The client has a location<br>
>> >>>>>>>>>> The client has an alias<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> Prodoctor Admin client<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> The admin client can create a new lead :<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> A lead consist of a name and a location<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> The admin client can query for Sales Agents based on :<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> Status<br>
>> >>>>>>>>>> Location<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> The admin client can assign a lead to a selection<br>
>> (1..n) of sales agents,<br>
>> >>>>>>>>>> this will send out the notifications.<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> The admin client manage the Sales Agents DB.<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> _______________________________________________<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> aerogear-dev mailing list<br>
>> >>>>>>>>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
</div></div>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> >>>>>>>>>> <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>
</div>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> >>>>>>>>>> <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>
>> >>>>>>>>> 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>
</div>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> >>>>>>>>> <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>
</div>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> >>>>>>>>> <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>
>> >>>>>>>> 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>
>> >>>>>>> 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>
</div>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> >>>>>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>> >>>>>><br>
>> >>>>>> _______________________________________________<br>
>> >>>>>> aerogear-dev mailing list<br>
>> >>>>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
</div>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> >>>>>> <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>
>> >>>>> 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>
</div>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> >>>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>> >>>><br>
>> >>>> _______________________________________________<br>
>> >>>> aerogear-dev mailing list<br>
>> >>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
</div>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> >>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>> >>><br>
>> >>> _______________________________________________<br>
>> >>> aerogear-dev mailing list<br>
</div>>> >>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> >>> <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>
>> >> 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>
</div>>> >> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> >> <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>
</div>>> > <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> > <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>
</div>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> <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>
>> aerogear-dev mailing list<br>
</div>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</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>
</div>abstractj<br>
<div class="HOEnZb"><div class="h5"><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>
</div></div></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>