Agreed +1
Let's get rid of Javanisms into JS land :)
Kris Borchers wrote:
>
> On Jul 19, 2013, at 9:24 AM, Lucas Holmquist
<lholmqui@redhat.com<javascript:;>
> <mailto:lholmqui@redhat.com <javascript:;>>> wrote:
>
>>
>> On Jul 19, 2013, at 6:41 AM, Sebastien Blanc
<scm.blanc@gmail.com<javascript:;>
>> <mailto:scm.blanc@gmail.com <javascript:;>>> wrote:
>>
>>> That is really cool !!
>>> Just make sure we are in sync with this "old school" Java Sender
and
>>> especially the fluent API
>>>
https://github.com/aerogear/aerogear-unified-push-java-client
>>
>> indeed.
>>
>> but i don't think in node you would do something like this:
>>
>> UnifiedMessage unifiedMessage = new UnifiedMessage.Builder()
>> .pushApplicationId("c7fc6525-5506-4ca9-9cf1-55cc261ddb9c")
>> .masterSecret("8b2f43a9-23c8-44fe-bee9-d6b0af9e316b")
>> .alert("Hello from Java Sender API, via JUnit")
>> .sound("default")
>> .build();
>>
>> // send it out:
>> defaultJavaSender.broadcast(unifiedMessage);
>>
>> you would just pass an object
>>
>> agSender.sender( url )
>> .broadcast( message, options )
>> .on( "success", function( response ) { … })
>> .on( "error", function( error ) { … } );
>>
>>
>> i think the "fluent" concept differs slightly in the 2 languages
>
> +9001 Your way is much better for the node world!
>>
>>>
>>>
>>>
>>> On Fri, Jul 19, 2013 at 3:25 PM, Matthias Wessendorf
>>> <matzew(a)apache.org <javascript:;>
<mailto:matzew@apache.org<javascript:;>>>
wrote:
>>>
>>> kick ass!
>>>
>>>
>>> On Fri, Jul 19, 2013 at 2:19 PM, Lucas Holmquist
>>> <lholmqui(a)redhat.com <javascript:;>
<mailto:lholmqui@redhat.com<javascript:;>>>
wrote:
>>>
>>> hello people,
>>>
>>> so i started a node version of the push sender api
>>>
>>> here is the JIRA for tracking
>>>
>>>
https://issues.jboss.org/browse/AGPUSH-181
>>>
>>> and the link to my repo for those who are lazy( like me )
>>>
>>>
https://github.com/lholmquist/aerogear-unified-push-node-client
>>>
>>>
>>>
>>> I understand there is a PHP client started,
>>>
>>> Tommy, could you post the link to the repo in this thread and
>>> create a JIRA to track if it's not there already
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev(a)lists.jboss.org <javascript:;>
>>> <mailto:aerogear-dev@lists.jboss.org <javascript:;>>
>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog:
http://matthiaswessendorf.wordpress.com/
>>> sessions:
http://www.slideshare.net/mwessendorf
>>> twitter:
http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev(a)lists.jboss.org <javascript:;> <mailto:
aerogear-dev(a)lists.jboss.org <javascript:;>>
>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev(a)lists.jboss.org <javascript:;> <mailto:
aerogear-dev(a)lists.jboss.org <javascript:;>>
>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org <javascript:;> <mailto:
aerogear-dev(a)lists.jboss.org <javascript:;>>
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org <javascript:;>
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org <javascript:;>
https://lists.jboss.org/mailman/listinfo/aerogear-dev