That sounds nice. I'm totally in favour of handling this different in
the webservice: its a different domain.
Computers will do
for bug in ubuntu.bugs:
...
Users simply can't ;)
As for whether answering all ubuntu bugs in a single webservice
request makes sense - I think it would, if we removed some
limitations, and partitioned apis out (I want to anyway). However, if
we can batch without the O(N^2) which you suggest a nice strategy for,
one of the strong motivations for not batching in the webservice goes
away.
That sounds nice. I'm totally in favour of handling this different in
the webservice: its a different domain.
Computers will do
for bug in ubuntu.bugs:
...
Users simply can't ;)
As for whether answering all ubuntu bugs in a single webservice
request makes sense - I think it would, if we removed some
limitations, and partitioned apis out (I want to anyway). However, if
we can batch without the O(N^2) which you suggest a nice strategy for,
one of the strong motivations for not batching in the webservice goes
away.