dallbee
Joined 12 years ago
Joined 12 years ago
I see this all the time with VPNs. By having everything behind the company VPN, application security isn't taken as seriously. As a result, lateral access becomes trivial at these companies.
Keeping everything public internet exposed from the start actually results in better security.
This gives you a key benefit of protobuf, without needing external schema files: you don't have to pay the space of the keys of your data.
This is simply not something you can do with JSON, and depending on your data can yield substantial space savings.
The maintenance burden for Stack cannot have been significant, and yet I guess I am unsurprised to see Google add another good app to their graveyard.
What do others use for this purpose?
My approach with my kids has been to use antibiotics only if there's no progression (better or worse). I figure as long as it appears the immune system is doing its job, that's enough for most cases.
So far, we've given our 3-year antibiotics on two occasions. Once for an ear infection that wouldn't clear and for when he had pneumonia.
Specifically, we noticed lack of support for these features:
- session trunking (and, in general, multiple channels)
- multiple concurrent requests on a channel (ala ca_maxrequests)
- callbacks
ca_maxoperations was quite low (10, I think?), and they limit the number of parallel clients that you can access EFS with at once.
What this amounts to is that you can reach acceptable performance on file reads/writes, but metadata heavy access patterns have no hope of reaching the advertised IOPs. It's a shame because frankly metadata performance is something NFSv4 excels at.
Is this limited to their higher end models?
There's nothing wrong with fixing a bug you discover upon inspection. Forcing tickets for every change discourages code maintenance.
Incredible.