What makes this a problem? The initial request to Polyglot is also "push".
The rest of the web works on "push" too; pull in this case would only help if you don't care that a request could take a long time (seconds) to resolve.
I didn't see mention of it, but what happens if a message is not responded to? How does Polyglot handle time outs?
If the goal is the ability to have certain routes processable by different languages/systems you could achieve this with reverse proxying (from eg. nginx) [1].
That way you can leverage any existing language frameworks and run them as standard HTTP responders. No need to work with a queue (and add it to the stack).
You can still limit the HTTP methods each proxy responds to as well [2].
I had to do the same thing from NameTerrific but got my migration code from the top-level.
The worst part is that I was "in contact" with the owner via Twitter, and he assured me that he would totally look into things at some point in the near future..
Mainly because the checksum is a very good source of truth. Not every file you get is named correctly, or the same as originally intended.
Regardless of the checking method, will there be an API to add episodes to a personal list, regardless of check sum or filname checking?
Next feature: notification of new episodes, particular by collecting group?
These are pretty much the 2 killer features I personally use AniDB for. The back end code for me is less important, because everything I need it to do, is being done. :)
What does this have over AniDB? I'm seeing MyAnimeList mentioned in the comments, but not AniDB?
Do you guys have an API checking file hashes/fingerprints against episodes to add to your list etc? That's one of the biggest draws for AniDB (for me).
Answering the question specifically: Yes. Same as if you were in say, construction, and you were expecting crane operators to bring their own cranes. A dentist their own drill. A chemist their own centrifuge.
In terms of the debate: Eventually you'll need to have policies in place around ownership of work produced, and while there's nothing preventing an employee from copying files to a personal device, having everything they work on stored on hardware owned by the company makes it significantly easier for the company to enforce those policies.
If you supply standardised equipment (a particular model, operating system, etc) it will also help for the setup of any new employee, and any interoperability that may be required. Everyone will get the same; troubleshooting requires a focused spectrum of knowledge and experience rather than knowing how to troubleshoot Windows, Mac, Bootcamp, Ubuntu, CentOS, on desktops or laptops.
I'm dubious as to the worth of these as a specific kitchen utensil; most how-to videos I've seen include a jumper as the sole "equipment" required. Maybe two rubber bands on either side to help prevent movement would make it even easier.
> The design process took months of careful exploration and testing. We did loads of sketches and built functional and aesthetic models by hand and on the computer.
The resulting product is quite nice aesthetically, but is it worth $18?
I don't recall ever reading that just because you have tests, you should no longer understand the processes by which your code functions. Was this something that they've seen happen, or experienced personally?
In contrast to direct database access, the HTTP implementation of the abstraction layer performed significantly worse. This will have also been part of the abstraction library having to parse/run the logic as well (nginx + PHP).
From memory, after trying the entire abstraction layer, I boiled it down to as small a file as possible for testing purposes (ie. a single PHP file that took the call and stored it into the DB, no configuration, removing as many "variables" as possible).
I was headed down a similar path myself, but luckily I was writing a completely new library that would abstract a lot of key-value stores. Before we used it in production, I performance tested it - HTTP is really slow. The end result was a client library that talked directly to the stores using adapters for the abstraction.
The majority of users/web requests aren't going to be hitting your hosting; they'll stop at the CDN.
Perhaps a better question is "fastest CDN?".