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 : Novell (NOVL) dirt cheap, good buy? -- Ignore unavailable to you. Want to Upgrade?

To: Scott C. Lemon who wrote (30258)	2/11/2000 11:31:00 AM
From: Paul Fiondella	Read Replies (1) \| Respond to of 42771

The EU investigation Of course we need to know what they are looking into specifically and we will know after someone posts the specific complaint lodged with them that caused the announcement of an investigation, but they are pointing to AD in their press releases. As you point out, "ADSI API's are only Windows API's". Therefore if you use AD for development and ADSI, you are writing for a Windows not a UNIX environment. You also say that Novell supports ADSI. Do you mean that a developer can write applications that use ADSI and have them run on a Netware server? Or are you saying that to write using ADSI you have locked yourself into a Windows environment? The next level of this question would be, is it as easy to use ADSI and write an application that uses NDS, e-directory etc. etc. as it is to use AD? Or are there quirks? "One of the most familiar open programming APIs is Open Data Base Connectivity (ODBC). ODBC provides open interfaces for relational databases, thus allowing developers to write applications and tools that work with any database that supports ODBC. Because of the thriving ODBC development community, every major relational database now supports ODBC. ADSI is the equivalent of ODBC for directory services. " That is what Microsoft says. Is it true? Is ADSI open and extensible by reference to a standards committee? Who controls how well ADSI works with LDAP or NDS? Is it possible that MSFT will throw in some flaw that only manifests itself when you use none AD directories? Could they optimize their ADSI only for their AD and exclude the possiblility of optimization for other directories? How much of this should be permitted from a monopoly? ======== It seems to me that Microsoft has a path for directory applications developers that first excludes all non-Windows platforms for development. Second is the question of how open they have been with Novell with those ADSI API's? Am I asking the right questions yet?