[gpodder] Re: Issue using API Method - Device Updates
- From: Thomas Perl <th.perl@xxxxxxxxx>
- To: gpodder@xxxxxxxxxxxxx
- Date: Sat, 3 Nov 2012 01:06:46 +0100
2012/11/3 Brian Bourke-Martin <brianbourke75@xxxxxxxxx>:
> Well, I just tried it in my browser and it continues to return non-empty
> contents on the third attempt, so I think something has either changed since
> the documents were writen in the API or there is a bug.
Sounds like a bug to me then. Please file a bug at
http://bugs.gpodder.org/ (gpodder.net product, Advanced API component)
and I'm sure Stefan will have a look at it in the next few days. If
it's not a bug in the API itself, it's a documentation bug, and we
have to fix that.
Thanks,
Thomas
> On Fri, Nov 2, 2012 at 7:51 PM, Thomas Perl <th.perl@xxxxxxxxx> wrote:
>>
>> Hi Brian,
>>
>> 2012/11/2 Brian Bourke-Martin <brianbourke75@xxxxxxxxx>:
>> > In the documentation it says that the time stamp in the
>> > return data should be sent back upon further calls to this function, but
>> > when I do two calls in a row (the first one with timestamp=0) the second
>> > returns a lot of information where I would expect it to be empty since
>> > there
>> > have not been any modifications since the previous update call. Am I
>> > doing
>> > something wrong or misunderstanding?
>>
>> We'll have to wait for Stefan's reply for a definitive answer. Until
>> then, you could try out the following:
>>
>> What happens at the third call with the timestamp returned by the second
>> call?
>>
>> Thanks,
>> Thomas
>>
>
Other related posts: