API Chatter

[id3nt1ty]

Cheers Gandalf.

I'm not sure if I made myself clear about the HTTP response codes though. At the moment BBDB always replies with a HTTP status of 200, regardless of whether the request was successful or not. This is different from the code you are returning as part of the request body. There is a section about them in that link I posted which gives examples of the general cases, and a more exhaustive list on wikipedia. It would be quite useful if they could be used, and probably not a big task.

I'm currently working on the SVG generation, but it's behaving a bit differently with the server-side code I'm trying to write than it did in the browser based proof-of-concept.

[Gandalf]

I saw that, took it in, and replied saying I would file away for future reading. API development still follows the same theory I mentioned earlier - you've got enough to be doing something, once you've got something to show for it I can look at adding extra functionality. You can work with what you've got for now, yes...?

The dev work I just did wasn't new feature, it was fixing what I had meant to do but failed to do (the no match id thingy).

[id3nt1ty]

Yes, I was just making my request clear. Not expecting it to be done last night.

[Gandalf]

OK.... yes we're singing from the same song sheet then.

Today I've activated logging on the API calls, so I can see who is calling what when, and how quickly (or slowly) the request is served. Varies wildly from 9ms to 60ms in testing. Hurrah for gathering data.

[id3nt1ty]

My match report project now has a task list and a first release milestone to aim for.