vfaronov

10 ms·

31.
by vfaronov 9y ago
H2O also allows an HTTP/1.1 backend to push by sending links [1] with rel=preload — these links are automatically converted to pushes by H2O. This can be further sped up with early hints [2]. [1] https://tools.ietf.org/
32.
by vfaronov 9y ago
There is ongoing work at the HTTP working group to standardize “cache digests” to solve this problem: https://tools.ietf.org/html/draft-ietf-httpbis-cache-digest
33.
by vfaronov 10y ago
I’m not sure what the author thinks “the web” is. For me, sites like Mic , Teen Vogue , CNN constitute a minor part of “the web”. Their being equated with “the web” seems like a much more serious problem than their visual design could e
34.
by vfaronov 10y ago
I’m sure this can all be done in Excel... except I don’t know how, and will sooner reach for Python when faced with a task like this. Definitely will have a look when a Linux version is available.
35.
Show HN: Turq – mock APIs and Web sites in seconds(github.com)
2 points by vfaronov 10y ago|0 comments
36.
by vfaronov 10y ago
> In that sense, REST in practice has always been just RPC without a clear spec for procedure call like XML or JSON RPC. HTTP, even when used without hypermedia, still has interesting features that are not found in traditional RPC. For
37.
by vfaronov 10y ago
Curious that they don’t mention HTTP conditional requests [1] even in passing. This mechanism is typically used for slightly different things, but you can, for example, make a PATCH request “idempotent” (in their sense) by adding an If-Matc
38.
ASTsearch: Intelligently search in Python code(github.com)
3 points by vfaronov 10y ago|0 comments
39.
by vfaronov 10y ago
I have a custom implementation of the popular “cheat sheets” idea, optimized for not leaving the zone. My sheets are short snippets of reStructuredText. When I press Win+H, my tool pops up in a small window, asks me for a keyword, and then
40.
by vfaronov 10y ago
> All four of the other browsers use effectively the same APIs — Safari is potentially going to change that in some ugly ways. I understand a developer’s desire to have more reach with less work. But if all browsers have the same APIs,
41.
by vfaronov 10y ago
Not bothering with TLS for a blog is likely to be a good idea.
42.
by vfaronov 10y ago
Since everybody's piling on their favorite alternatives, I have to mention HTTP Prompt [1]. It's obviously in another league than Insomnia and such, but I find that it strikes a sweet spot: much more convenient than curl or HTTPie
43.
by vfaronov 10y ago
Yes, DRF was one of those. But I don't remember whether I ran the whole test suite or only some subset of it that I could (quickly) get to run at all :) My goal was to get a sense of what it would look like on a realistic project, not
44.
by vfaronov 10y ago
I ran some of the tests for a few of Django's more popular API and CMS frameworks, instrumented with HTTPolice. I found a few minor bugs, but nothing interesting enough to report. Like, one of them responds to an OPTIONS request with 2
45.
by vfaronov 10y ago
Right. I just checked and HAR 1.2 seems to work pretty well. A small nuisance is that Fiddler synthesizes bodies with debug information on CONNECT requests and responses, but I'll work around that in the next release. But experience wi
46.
by vfaronov 10y ago
Thank you, I'm very glad to read this. > I need integrate this into our pre-production environments like yesterday! Please feel free to share your experiences. The integration story here clearly needs more work, and it would be quit
47.
by vfaronov 10y ago
> We're talking about REST best practices here, not "let's do RPC instead". I don't think so. Avernar above seems to argue against REST as an architectural style (RPC being the default as everybody uses it). I th
48.
by vfaronov 10y ago
It also doesn't provide much benefit over a plain RPC-like interface, because, for practical reasons, the webcam will be coded to send requests directly to https://example.com/report-problem and https://exam
49.
Show HN: Lint for HTTP(github.com)
138 points by vfaronov 10y ago|12 comments
50.
by vfaronov 10y ago
True, and some of these use cases are very interesting. jcrites does not mention them, though. I realize now that his comment does not preclude them, either, but still this example would be more convincing if automated clients were emphasiz
51.
by vfaronov 10y ago
Are you suggesting that Fielding did not intend REST to be used in automated systems? By "distributed hypermedia systems", did he really mean "alternative browsers for alternative WWWs"?
52.
by vfaronov 10y ago
The big problem with using the hypertext Web as an example of REST is that there is a human operator literally driving that "engine of application state". Most API clients cannot afford to compute their state transitions on a netw
53.
by vfaronov 10y ago
This is pretty much the crux of the problem that the Semantic Web / Linked Data folks have been working on for years. They have the technology to do it (RDF). This technology is not widely used for a number of reasons, but "becaus
54.
by vfaronov 10y ago
A side benefit to having separate, clearly named functions: they often play better with tools. You can jump to them by name from a completely different part of the code (with some editor support). You see them in the headers of your Git hun
55.
by vfaronov 10y ago
How is this more "Chrome-sans-Google" than Chromium itself?
56.
by vfaronov 10y ago
This must be the most elegant vulnerability I've seen in ages. It almost feels like the pieces are interacting as designed. You politely ask the server to use a proxy -- and it does!
57.
by vfaronov 10y ago
Somehow it's strange that a language difference as modest as between Python and Ruby should isolate people to the point where they can't fit in even on a 12-week retreat. I mean, that would probably happen to me if I went to a Rub