nla / chropro Goto Github PK

This way as the API (and our implementation) evolves we can see the code change to potentially find regressions with tools like git bisect.

#6 moved context creation into init() but it's still disposed on every single request in the finally block in render(). Not sure why we're not seeing issues from that.

I think we should be creating a new context each time so that we don't preserve cookies etc across requests.

We will need to have a decent testing strategy.

There is the aspect of whether it works with chrome or not and then there is just the basic protocol interaction.

For now we might want to test just the protocol aspect. To make sure the encoding/decoding works.

Need to get a build in maven central so we can depend on it...