ChrisAtWork

5 ms·

1.
by ChrisAtWork 8y ago
Same. My home Unifi network is all integrated with PiHole and does DNS over HTTPS to CF. Having the 1.1.1.1 on my phone is great except when I'm at home and want it disabled.
2.
by ChrisAtWork 10y ago
Why do you think HTTPS would fix this? For the TLS case, there are enough MITM proxies, both in the Enterprise and elsewhere, to make this a real concern. There are also API Aggrigators which are effectively MITM and need to be taught to &q
3.
by ChrisAtWork 10y ago
The "?api-version" approach in the doc is there for exactly the reason you call out. Azure uses this approach. By omitting "/v1.0" from the path it makes the actual URL's far more durable, as they're not v
4.
by ChrisAtWork 10y ago
I don't think I've ever seen delta's done at-scale with actual temporal tables, but rather with transaction Id's of some sort. For example (based on the doc) when you register a delta link, there's a row written to
5.
by ChrisAtWork 10y ago
There's nothing wrong with RPC APIs. Other than being "Not Cool" due to the legacy of SOAP, they can deliver some very nice value. Various RPC mechanisms like Bond and Protocol Buffers (and more recently GRPC) are trying hard
6.
by ChrisAtWork 10y ago
There are a number of examples to cite showing what you say isn't true. Allowing totally arbitrary OData $filter expressions does lead to problems, but recent versions of OData have a nice mechanism to describe (and discover) what can
7.
by ChrisAtWork 10y ago
That particular example was chosen not because of OData, but because it required someone to type in a horribly long set of alphanumeric codes. There's no way a human can effectively type that, nor is there any real way to look at it an
8.
by ChrisAtWork 10y ago
Delta queries are pretty easy, assuming you have a rich data store behind your data. As others have said, your data store needs to be able to say, "Show me changes since XYZ". Most of the Big Apps can do that, and from there the p
9.
by ChrisAtWork 10y ago
It turns out that uploading files is hard. Files come in a variety of sizes, networks sometimes don't work, browser processes come-and-go, some users expect restart semantics, some don't...
10.
by ChrisAtWork 10y ago
"Success With Info" is something that just causes problems. The number of examples we found of "Success with Info" going horribly wrong was abundant. Turns out checking return codes is something people have failed to do
11.
by ChrisAtWork 10y ago
The API version header has a few problems. 1. Older proxies used to remove/strip headers they don't understand. 2. Frameworks and libraries don't always give access to n non-standard headers, meaning they just can't use