[Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue
matzew at apache.org
Thu Jan 19 03:09:01 EST 2017
Why was this removed? It's a key part of the demo. Not sure I recall any
discussion around removing this :-(
On Wed, Jan 18, 2017 at 10:22 PM, Daniel Passos <dpassos at redhat.com> wrote:
> This features was removed by me. For more details here is where
> magic happened
>  https://github.com/aerogear/aerogear-android-cookbook/commit/
> On Wed, Jan 18, 2017 at 7:08 PM, columfoskin <columfoskin at gmail.com>
>> Hey all,
>> I am working on building a Node js version of the backend for the Aerodoc
>> application and have some questions if anyone can help it would be great.
>> Can anybody help me to understand when the lat/long pairs are sent from
>> android device to the Aerodoc backend? I have spent some time debugging
>> trying to figure this out - without much success.
>> I have been looking at the request sent from the android app on login and
>> is not then. My guess from looking at the Java code is this happens when
>> when a HTTP PUT is called on the ’saleagents’ endpoint but I cannot
>> determine when that endpoint is hit (from looking at the code &
>> Also, from what I see, updates to the agents status are sending a POST to
>> the backend, and not a PUT and therefore hitting my POST endpoint -
>> issues. Is this expected behaviour?
>> Any insight or help appreciated.
>> View this message in context: http://aerogear-users.1116366.
>> Sent from the aerogear-users mailing list archive at Nabble.com.
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
> -- Passos
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Aerogear-users