meaty

58 ms·

241.
by meaty 14y ago
Nice solution.
242.
by meaty 14y ago
We use a keychain system for that and store the public key in active directory. That allows us to revoke at a per user level all keys. We do a lot of integration and use 25 different external APIs including s3. BAsically, we don't use glob
243.
by meaty 14y ago
Actually, having no passwords and using a platform which supports integrated authentication (like Windows) is probably the best approach with respect to handling this. The authentication requirements are handled at an infrastructure level,
244.
by meaty 14y ago
A few comments: 1. We're probably not going to use it unless we can host it ourselves because we can't possibly risk information leaking out of the infrastructure and being thrown god knows where. 2. If all it does is IIS/ASP.Net applicatio
245.
by meaty 14y ago
Also useful when MongoDB blows chunks because it was a crap architectural decision and you quickly port your app to raw SQL...
246.
by meaty 14y ago
You mean: stop bundling crapware with our crapware! Note: I have no problem with Java on the server or client, just the applet and browser plugin model.
247.
by meaty 14y ago
Try shipping it with your product in about 5 years...
248.
by meaty 14y ago
Agreed - this is not HP's responsibility.
249.
by meaty 14y ago
What country are you in? I'm talking about UK support, so you might have better luck in another country.
250.
by meaty 14y ago
It will happen. It better do as I'm an ARM Holdings shareholder. It has happened before. I had a 32-bit ARM desktop once: http://en.wikipedia.org/wiki/Acorn_Archimedes
251.
by meaty 14y ago
It's actually pretty nice. We have some cool stuff deployed with it (long term service correlation, long running background processes, custom workflows for business processes), but you are right about it being complicated. We're in the fina
252.
by meaty 14y ago
We built a massive state machine based workflow in WF3. It has limped along until .Net 4.0, but we've hit a brick wall now as they have killed the following assemblies in .Net 4.5 (all legacy WF3/3.5 assemblies basically): System.Work
253.
by meaty 14y ago
It took the scientists as little 2^23 sessions to extract the entire contents of a TLS session cookie That's half a million sessions. I think an attack is possibly unlikely.
254.
by meaty 14y ago
At least you can fork it internally though and support it if need be. The same is not the case with something like XNA which is so tied into the OS that when they drop it, you're up shit creek.
255.
by meaty 14y ago
Same trouble here and I'm getting pissed off with it. We got fucked by Windows Workflow and Silverlight, both of which were canned. The former was rewritten completely but didn't support our use cases any more. The main thing for me is that
256.
by meaty 14y ago
Apart from ARM that is :)
257.
by meaty 14y ago
That doesn't work for graphics drivers as there is a different driver model for Windows 8 than Windows 7.
258.
by meaty 14y ago
Bollocks - they are just as shit with respect to support.
259.
by meaty 14y ago
This is normal for Microsoft product-specific APIs. They are as stable as a drunk unicyclist from experience. Well to be truthful, they last forever but you never know which one you should be using because there are about 3-4 concurrent API
260.
by meaty 14y ago
We've had similar issues. You usually just threaten to "come to fucking <insert country> and burn the support center down" and they will escalate it to the right people and it will get resolved. Fine example: Sony just replaced my s
261.
by meaty 14y ago
HP doesn't write or supply any drivers - they are all 3rd party packages rewrapped by HP.
262.
by meaty 14y ago
That is true apart from Intel Graphics.
263.
by meaty 14y ago
Contrary to this, I'm still getting driver updates for my 2007 ThinkPad T61.
264.
by meaty 14y ago
HP warranties and support are just as bad for corporate customers. It's easier to just buy parts from Misco and fix it yourself most of the time. That goes for everything from desktops to high end servers. Sony service stinks as well. Lenov
265.
by meaty 14y ago
The same factories will produce different quality items depending on the design and how much they get paid. Not an anecdote for once... One of our clients is a large insurer who have just dumped HP due to reliability problems. They have app
266.
by meaty 14y ago
The irony is that Microsoft made it even easier to steal stuff by forcing complete market dominance. It's easy to steal if everything is compatible and connected i.e the DOS/Windows monoculture.
267.
by meaty 14y ago
If anyone has ever owned an HP laptop of any description recently, they will know not to go near this, not even with a 20 foot long stick. Absolutely shoddy machines from end to end.
268.
by meaty 14y ago
Yes they are notorious spammers.
269.
by meaty 14y ago
Fair point - I stand corrected! :)
270.
by meaty 14y ago
You can do this with Microsoft Exchange already, but not standard SMTP etc.

More ›