Adam Retter

@cowtowncoder I think this is most likely the equivalent of setting the property `http://apache.org/xml/properties/internal/entity-resolver` and providing an `org.apache.xerces.util.XMLCatalogResolver` in Xerces. I am switching eXist-db from Xerces to Woodstox (keeping to...

@cowtowncoder Also can you tell me how to setup an XMLResolver equivalent for the SAX API in Woodstox? I need something akin to `org.apache.xerces.util.XMLCatalogResolver`

@njlr Hi there, I was initially interested as I make some contributions to RocksDB and I wondered about packaging that. Unfortunately if I understand correctly, then we would also have...

Any documentation on using `osslsigncode` please?

So if I understand there are two main drivers here: 1. Split the legacy `send` function into constituent methods; Whilst also offering a `send` variant that takes a Map of...

So a few questions: 1. I don't really understand why you would want functions for a POST or PUT request without a body? 2. The structure for the request does...

1. So I do like your idea of the *request* and *response* being the same format. Maybe it is enough to rename `$options` to `$request` (or even `$data`). 2. I...

> The boundary key for multipart messages, which the previous specs had and which I adopted in the first draft, should probably be skipped anyway, as it’s something the implementation...

1. Your first section regarding the Content-Type header sounds very reasonable. Just one question there still remains from above: > iv. map(*) could be serialized as JSON. Whilst I like...

@olamy @khmarbaise Any chance of getting some review on this? I included all the good stuff (tests, passing CI) ;-)