Directories do this all day long. It's just a protocol implementation.
The question is, when is this mechanism going to emerge, and how do you get people to use it?
Gas Core Nuclear Rocket
on
On to Mars
·
· Score: 1
Some very smart guys at Los Alamos are working on a Gas Core Nuclear Rocket.
This rocket engine will use a fissioning uranium gas plasma to create ungodly amounts of thrust--something on the order of 10,000 SpI. According to the scientist I talked with who has been working on the design, a GCNR-powered ship could be very lightweight, carry hundreds of crew members and thousands of tons of payload, and still travel to Mars within thirty days or so.
This thrust is on the same order as the Freeman Dyson/Stanislaw Ulam "Orion" rocket, basically a bunch of well-timed nuclear explosions transferring kinetic energy to a graphite-coated pressure plate that provides the thrust.
Of course, the antinuclear zealots will try to stop this engine from being built, saying things like "Oh, it'll pollute space with nuclear waste products" or some such tripe. But this technology is too good to pass up.
The biggest obstacle to date in building a GCNR is the computational power needed to model the extraordinarily complex interactions of the reaction, basically the same as modelling a nuclear explosion. Obviously we are getting closer to being about to pull off the analysis, given that we are nearing (or at) the point where we can model explosions and wean ourselves off of underground testing.
I like the idea of a Zubrin-style "live off the land" approach, and maybe we should try that now since that's what we know we can do this minute. But the U.S. should also throw a lot of money at the GCNR, build a ship with enough supplies and crew, and colonize Mars without dicking around.
This is good. But I didn't see any notion of referential integrity in the spec.
The biggest problem with the web is that we will still have to manage links manually. I hope someone takes the bull by the horns and figures out how to eliminate (or at least mitigate) the "404 Not Found" problem. Perhaps that now-open-source Udanax code could be mined to turn up some good algorithms?
Another good idea (but really an unrelated spec) would be a file system redirector architecture that enabled all documents (per user preference, of course) to vend docs automagically via an HTTP or "blocks" server.
Kerberos is an authentication mechanism. It is simply a way of proving you are a valid network user. Try this link for more info about Kerberos and what it does.
NDS is a directory service. It contains and replicates all information about network users, groups, computers, and other resources on the Net.
NDS uses its own authentication mechanism as well as standard LDAPv3 authentication. ADS uses Kerberos and might even use standard LDAPv3 as well. I should try it sometime using the JNDI LDAP providers we use just to see for myself.
NDS uses multimaster replication, which enables you to have multiple directory masters on your network sharing and updating information. This means all directory information looks the same, no matter from which server you are connected to.
Multimaster replication is very nice for running a large company, as it guarantees referential integrity of all your directory information, no matter how big the company or how physically disparate are your branch offices.
Note that referential integrity is part of NDS: it has no "404 Not Found" equivalent.
NDS V8 scales up to a billion objects in the database, so you could theoretically create user objects for everyone on Earth in six or seven directories, although I would probably just use the two or three NDS servers in my house. =)
We announced NDS for Linux, so you will be able to run it on your favorite Linux distro and redirect all authentication requests into NDS.
Sorry if I sound like an informercial--I live this stuff.
Hope that helps.... =)
............ kris
Kris Magnusson Open Source Architect Novell, Inc. Coauthor, Java Enterprise in a Nutshell O'Reilly & Associates
Slashdot Mirror
Directories do this all day long. It's just a protocol implementation.
The question is, when is this mechanism going to emerge, and how do you get people to use it?
Some very smart guys at Los Alamos are working on a Gas Core Nuclear Rocket.
This rocket engine will use a fissioning uranium gas plasma to create ungodly amounts of thrust--something on the order of 10,000 SpI. According to the scientist I talked with who has been working on the design, a GCNR-powered ship could be very lightweight, carry hundreds of crew members and thousands of tons of payload, and still travel to Mars within thirty days or so.
This thrust is on the same order as the Freeman Dyson/Stanislaw Ulam "Orion" rocket, basically a bunch of well-timed nuclear explosions transferring kinetic energy to a graphite-coated pressure plate that provides the thrust.
Of course, the antinuclear zealots will try to stop this engine from being built, saying things like "Oh, it'll pollute space with nuclear waste products" or some such tripe. But this technology is too good to pass up.
The biggest obstacle to date in building a GCNR is the computational power needed to model the extraordinarily complex interactions of the reaction, basically the same as modelling a nuclear explosion. Obviously we are getting closer to being about to pull off the analysis, given that we are nearing (or at) the point where we can model explosions and wean ourselves off of underground testing.
I like the idea of a Zubrin-style "live off the land" approach, and maybe we should try that now since that's what we know we can do this minute. But the U.S. should also throw a lot of money at the GCNR, build a ship with enough supplies and crew, and colonize Mars without dicking around.
Here's a link explaining more about the GCNR.
.......... kris
This is good. But I didn't see any notion of referential integrity in the spec.
The biggest problem with the web is that we will still have to manage links manually. I hope someone takes the bull by the horns and figures out how to eliminate (or at least mitigate) the "404 Not Found" problem. Perhaps that now-open-source Udanax code could be mined to turn up some good algorithms?
Another good idea (but really an unrelated spec) would be a file system redirector architecture that enabled all documents (per user preference, of course) to vend docs automagically via an HTTP or "blocks" server.
.............. kris
NDS is a directory service. It contains and replicates all information about network users, groups, computers, and other resources on the Net.
NDS uses its own authentication mechanism as well as standard LDAPv3 authentication. ADS uses Kerberos and might even use standard LDAPv3 as well. I should try it sometime using the JNDI LDAP providers we use just to see for myself.
NDS uses multimaster replication, which enables you to have multiple directory masters on your network sharing and updating information. This means all directory information looks the same, no matter from which server you are connected to.
Multimaster replication is very nice for running a large company, as it guarantees referential integrity of all your directory information, no matter how big the company or how physically disparate are your branch offices.
Note that referential integrity is part of NDS: it has no "404 Not Found" equivalent.
NDS V8 scales up to a billion objects in the database, so you could theoretically create user objects for everyone on Earth in six or seven directories, although I would probably just use the two or three NDS servers in my house. =)
We announced NDS for Linux, so you will be able to run it on your favorite Linux distro and redirect all authentication requests into NDS.
Sorry if I sound like an informercial--I live this stuff.
Hope that helps.... =)
............ kris
Kris Magnusson
Open Source Architect
Novell, Inc.
Coauthor, Java Enterprise in a Nutshell
O'Reilly & Associates