When I request a resource that is empty, I get something like the
following
<?xml version="1.0" encoding="UTF-8"?>
This example is from a call to GET the /expenses for a date when there
were none. I’m just wondering if there’s any scope to change this to
either be an empty list like
<?xml version="1.0" encoding="UTF-8"?>
or even 404 (Not Found)
As it is, I have to make a special case for unmarshalling which is a
bit of a chore :S
When I request a resource that is empty, I get something like the
following
<?xml version="1.0" encoding="UTF-8"?>
This example is from a call to GET the /expenses for a date when there
were none. I’m just wondering if there’s any scope to change this to
either be an empty list like
<?xml version="1.0" encoding="UTF-8"?>
or even 404 (Not Found)
As it is, I have to make a special case for unmarshalling which is a
bit of a chore :S
v2 will be live very soon - we’re just finalising the work on the
production infrastructure. We’ll post on here as soon as it’s switched on.
We’ll continue to keep v1 running for a while, but we’d encourage every
current app developer to migrate their apps over as soon as possible, and
all new apps should definitely use v2.
OllyOn Thursday, January 26, 2012 7:17:08 PM UTC, Toby wrote:
Thanks, that’s awesome. Not that I’ll hold you to it but when roughly
do you think v2 will be out in the wild? Are you planning to keep v1
running in parallel? I’m just trying to plan my upgrade path…
v2 will be live very soon - we’re just finalising the work on the
production infrastructure. We’ll post on here as soon as it’s switched on.
We’ll continue to keep v1 running for a while, but we’d encourage every
current app developer to migrate their apps over as soon as possible, and
all new apps should definitely use v2.
Olly
On Thursday, January 26, 2012 7:17:08 PM UTC, Toby wrote:
Thanks, that’s awesome. Not that I’ll hold you to it but when roughly
do you think v2 will be out in the wild? Are you planning to keep v1
running in parallel? I’m just trying to plan my upgrade path…
Thanks, that’s awesome. Not that I’ll hold you to it but when roughly
do you think v2 will be out in the wild? Are you planning to keep v1
running in parallel? I’m just trying to plan my upgrade path…
When I request a resource that is empty, I get something like the
following
<?xml version="1.0" encoding="UTF-8"?>
This example is from a call to GET the /expenses for a date when there
were none. I’m just wondering if there’s any scope to change this to
either be an empty list like
<?xml version="1.0" encoding="UTF-8"?>
or even 404 (Not Found)
As it is, I have to make a special case for unmarshalling which is a
bit of a chore :S