API Design Questions (4)

[Gervase Markham]

On 29/09/09 14:37, Max Kanat-Alexander wrote:
> 	The most important thing is that you return time zones.

Well, the current XML-RPC interface returns all times in the timezone of 
the server and makes you get timezone information via another call. I 
was planning to emulate that pattern. Have you changed your mind - are 
you now thinking it's better to return the timezone with each timestamp?

> 	I think so. For parsing, it's probably just easiest to include just the
> username. But maybe it'd be better to always include a full user object
> with username and fullname, because otherwise people will have to make
> one call per user to get their full name.

Right. So which shall we do? :-) I'm going to stick with full user 
object everywhere unless you say otherwise.

> (With XML-RPC it's easy to
> specify lots of users in one call, so this isn't a problem, but with
> REST I'm not sure it's as easy, and there's a limit on URL lengths.)

But we are talking about output here, not input. So there's no URL 
length issue.

>> * (It's OK if no-one knows this.) We don't provide product IDs or
>> component IDs on the legacy XML interface. Why do we provide
>> classification IDs? Should I remove them from the returned data?
>
> 	I think we provide all those IDs in config.cgi--I have no idea why we'd
> provide them in bug XML, though....

OK, I'll cut classification_id out of the returned data.

Gerv
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla