Decide on and document the HTTP API about keytransparency HOT 3 CLOSED

Good suggestion. I'll put together an API document

On Fri, Aug 21, 2015 at 10:11 AM, Andres Erbsen [email protected]
wrote:

The status of the internal protos seems to be approaching agreement, but
dmz and I only have a vague idea about the HTTP layer. We don't have
specific requirements for how this should work, so agreeing will probably
be not that hard, but it would still be nice to communicate this explicitly.

By "document" I mean something that people who don't speak goog.http
annotations can understand well enough to implement. It does not need to be
super formal or strict. Maybe just an explained example is sufficient.

—
Reply to this email directly or view it on GitHub
#82.

Gary Belvin | Software Engineer | [email protected] | Security Team

from keytransparency.

I can do that since I implemented the HTTP proxy.

from keytransparency.

Perfect.

On Fri, Aug 21, 2015 at 12:43 PM, Cesar Ghali [email protected]
wrote:

I can do that since I implemented the HTTP proxy.

—
Reply to this email directly or view it on GitHub
#82 (comment)
.

Gary Belvin | Software Engineer | [email protected] | Security Team

from keytransparency.