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?".
22 karma · joined March 7, 2013
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?".
It wasn't quite dynamic (it required an engineer to set new values for how many workers you wanted..) but we could do this via a GUI.
For (1) what do you do with the persistence? A web request, in general, is not important after a few seconds.
For (2) how does Polyglot accept multiple responders for a single request, and how would it join the responses?
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?
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].
[1]: http://nginx.com/resources/admin-guide/reverse-proxy/
[2]: http://stackoverflow.com/questions/8591600/nginx-proxy-pass-...
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..
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. :)
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).
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.
> 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?
http://www.quora.com/Node-js/Why-did-Koding-switch-from-Node...
Which would act as an incentive for them to work.
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).
EDIT: Direct database access over the network.