5 ms·
> if you can do it over http then you really should There seems to be some wisdom here that I am not extracting successfully. It seems HTTP "can" in most cases
by whacked_new 18y ago
> if you can do it over http then you really should
There seems to be some wisdom here that I am not extracting successfully. It seems HTTP "can" in most cases. But where it can, do you really want to use it? Technically you could also write a db engine that reads over HTTP, but this must be a terrible idea; what would be the argument here that counters the rule of thumb?
- jacquesm 18y agocan: - without getting really tortuous, but a little bit rethinking your problem should be fine - without sacrificing a large amount of speed or functionality - without compromising your design goals
- whacked_new 18y agoSafe to say then, that it's a case by case and so, not so much a rule of thumb?
- davidmathers 18y ago"Technically you could also write a db engine that reads over HTTP, but this must be a terrible idea" If you go to this url you can probably find some contact info to tell the NY Times people how terrible their idea is: http://code.nytimes.com/projects/dbslayer http://code.nytimes.com/projects/dbslayer