To: ToySoldier who wrote (11354 ) 10/16/1998 5:09:00 PM From: keithsha Read Replies (1) | Respond to of 74651
TTS is no more than a fix to NetWare's flawed disk caching algorithm. The apps you spoke use the dos commit call to ensure that data has been written to disk. NetWare's cache doesn't flush the data to disk upon commit and when the inevitable NetWare failure occurs the database the workstation app (foxpro, dbase, etc.) was managing is corrupted. The TTS hack requires that you specify files for which a transaction log is generated for file recovery. As for NLM flakiness, this is precisely the reason why the development community abandoned NetWare in spite of high NOS market share. It is too hard to write reliable NLM based apps. Even if your app is reliable, I've seen as many as 100+ utility and maintenance NLMs running on a server. Any of which may corrupt each other and abend the server. NetWare 4.11 allows apps to be isolated in ring 3 but you'll take 20% performance hit and Novell recommends that you do so only while testing. Java apps may improve this, but if the NetWare “Console1” app is any indication with a 40% performance hit just to run a system admin console, it may be too little, too late, and too slow. The reality is there are fewer than 30 real applications available for NetWare, such as Oracle8, Tengah's web-applications server and one or two Java-based database applications. The remainder of the 368 “applications” on the Novell web site are backup and network management utilities. Contrast this with Windows NT Server 4.0 that has over 4,000 true server-side applications, and 650 that are integrated with NTDS. Check out developer.novell.com Toy these are facts, not mean spirited rants. You have not responded to any of my challenges so it is obvious that you know nothing about NetWare other than PR hype and even less about NT. Keith