Slashdot Mirror
The Secure Public Data Repository?
jducoeur writes "So Hailstorm has died an unlamented death. But the demand for the idea of an information repository isn't going to go away -- users demand convenience, and this would be convenient. So here's a timely question looking for wild speculation: how would a truly secure, public data repository work? How would your data be stored? Would it be centralized or distributed? How would you grant access to specific elements within it? What would the business case for running such an archive be? Maybe if we can come up with a good design now, we can head off the next inevitable bad one..."
But the demand for the idea of an information repository isn't going to go away -- users demand convenience, and this would be convenient.
How 'bout a harddrive as an "information repository."
Noone is "demanding" centralized information repositories. WTH is an information repository anyway?
The average Joe computer user does't need a centralized data area with version control and the rest of the buzz words. The few corporate needs are already fullfilled with things like CVS and ClearCase -- not to even mention group ware suites such as phpGroupWare.
It's all buzzwords. Six months ago it was XML and Java this, CSS and JSP that. So today the buzz is dotNET and Hailstorm with their information repository, well, guess what? MS just found out that this particular buzzword is utterly useless and has dropped it.
We would do better to just forget these words even existed instead of trying to breath life into something that was never meant to live in the first place.
int func(int a);
func((b += 3, b));