Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : How high will Microsoft fly? -- Ignore unavailable to you. Want to Upgrade?

To: ToySoldier who wrote (11466)	10/20/1998 5:15:00 PM
From: keithsha	Read Replies (1) \| Respond to of 74651

Toy, you are some piece of PR spin. Misrepresenting the facts to this board, your peers and probably your customers. What is more disturbing is you think that architecture doesn't matter. The devil is in those "techno-babble" details and this is somehow unimportant to you. It is when building systems that people depend on. Of course, there is only one user object per user, but their are many supporting NDS objects that are also implemented. Machine, DHCP client, etc. The list goes on. So my statement stands, your examples of OBJECT counts don't relate to user counts now do they! As for your single domain FUD, OK, let's design a NetWare tree with a SINGLE partition. Now how far does that scale, 1-2000 objects max and it shouldn't span a WAN link according to Novell's recommendations. NetWare can scale to a limited size through incredibly complex partitioning and replication of the database and then constant repartitioning as the tree grows. Even more complexity given that you'll want some login fault tolerance and at least 2 replicas of each partition are recommended. Oh, and any external references such as groups, members, etc. should not span partitions or performance will suffer. THIS IS A DBMS NIGHTMARE! The 1400+ page NDS error diagnostics book says it all. Of course Boeing and Digital and many other customers uses multiple domains. Domains define a security and administration realm as well as a replication ring. They scale quite nicely into tens of thousands of user objects. These security realms then can be federated through simple trust relationships. So which is easier to manage and maintain? A granularity of 2K for NDS or 20K for Domains. A dozen trust relationships or hundreds of partitions. Granted domain objects cannot be extended with additional properties by the user, but they also do not suffer from the schema conflicts, inconsistencies, integrity errors and replication storms of a large NDS tree. As for Novell's non-real world demo at N&I, there are many ways to fake it. Dis-jointed identical trees on a round robin DNS, demo admin to a separate tree from login to isolate replication, populate a bunch of dummy objects and login attendees as guest. Besides, there is no admin beyond object creation and only a few thousand attendees and vendors may be logged in at any one time. So what does it prove? This ain't real world or audited since Novell owns a part of N&I. Facts, not FUD. Get your buddies to educate you on how NetWare really works and then come back and talk grasshopper. Keithsha