Antony Male

Also, why not submit a PR to OrmLite changing their IDConnection to a DbConnection? That should actually be backwards compatible...

Sorry for the delay, I was on holiday. Cheers for the heads-up. I haven't really played with composer, but am I right in thinking that a single `composer.json`, as in...

Yeah, having dug into it a bit more (there's no documentation for fuelphp 2.0 yet), it seems PSR-0 is one of the requirements, along with a set of (as-yet-undefined) fuel...

I'm not going to be at a machine with a web stack on it for a few days, but until then... Are you getting confused between the (confusingly named) inline...

One clarification: when you say "But now if I decide that I need to allow a module to output some inline JS", is that inline JS which can be put...

Protocol-relative URLs make sense for CSS files which are requested by the browser, as they avoid "This page contains both secure and non-secure items" warnings. However I can't see any...

Indeed, [that's the defined behaviour](https://github.com/canton7/RestEase#return-types). With JSON that's sensible behaviour, as a bare string is not valid JSON. My understanding is that the same is true for protobuf - it's...

If your endpoint is returning raw binary data, you really need to be subclassing [`Requester`](https://github.com/canton7/RestEase/blob/master/src/RestEase/Implementation/Requester.cs), and overriding [`RequestWithResponseAsync`](https://github.com/canton7/RestEase/blob/master/src/RestEase/Implementation/Requester.cs#L363) to **NOT** call `response.Content.ReadAsStringAsync()` - as that can and will fail if...

> Will close the issue as backward compatibility seems to put a full stop to this being changed... Reopening, as I want to think about binary requester support. > The...

No problem. I'm happy to update the README to clarify the stringy nature of most of RestEase, and point people who want to talk binary in the right direction (including...