SI
SI
discoversearch

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: Mitch Blevins who wrote (22095)5/5/1999 8:50:00 AM
From: ToySoldier  Read Replies (1) | Respond to of 74651
 
Hi Mitch,

I cant profess to intimately know much about SLURPD, but I believe I understand the difference between SLURPD and LDUP.

SLURPD is used to replicate/distribute common data within one X.500 specific tree. It is based on and an extension to LDAP. The issue is that with SLURPD, it is based on a Master/Slave and its main purpose is to allow a mechanism that places several replicas of the DS data to other servers so that the load can be better handled when more clients are putting demands on the TREE.

LDUP is a protocol that figures out how DIFFERENT X.500 based TREEs can effectively share common data between each other. This is a BIG difference since each unique TREE (which can be running on different X.500 vendors ie. NDS, Netscape, eNetwork, Active Directory, etc.) will likely have authority of different objects or attributes in an object, how does a protocol address this. SLURPD was never developed to address it since there is no dispute on which replica has the authority on the accuracy of the data.

The LDUP committee is being headed up by a NOVL DS Engineer (sorry I cannot remember his name).

So in conclusion I would say that although SLURPD is a critical component to LDAP-based DSes (like Netscape I would think) it does not address the needs trying to be addressed by LDUP. There will likely not be one DS vendor or protocol in the end of the DS evolution, so mature, industry accepted, open standard protocols will be needed (LDAP is likely the protocol of choice with more maturity) to allow different "Keystone" DSes to share data amongst themselves and to the requesting clients.

Hope that makes sense Mitch

Toy