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 : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?

To: micromike who wrote (8976)	4/10/1998 8:19:00 AM
From: John Carragher	Read Replies (2) \| Respond to of 64865

drudge report uncovers msft plot to send out mass support letters to the newspapers etc.per LA Times drudgereport.com

To: micromike who wrote (8976)	4/10/1998 8:21:00 AM
From: Scott McPeely	Read Replies (2) \| Respond to of 64865

Java NC's won't go anywhere until the stuff mentioned in the following link is done. computer.org "Data synchronization defines cooperating components to replicate, transport, and update application Java objects. These mechanisms are the basic framework that enables disconnected operation. Because Java objects must reside locally during periods of disconnected operations, some form of persistent memory is required. However, this requirement does not mean that a file system must be exposed to users or applications. Instead, data synchronization mechanisms will be available to software developers as a new set of Java APIs." ... Sounds like Microsoft NT5.0 Intellimirror feature ... "Adaptivity API The MNCRS supports the ability of applications and systems to change their behavior and environmental requirements according to prevalent conditions. This has a static, or semistatic, component (Registry) and a more dynamic component (Notification), as dictated by the rate of change in the environmental conditions being monitored. Registry: Defines a repository of properties in Java. Notification: Provides the dynamic component by allowing applications or system components to register interest in certain conditions that are bound to change frequently (perhaps once during a user's session). These conditions include system isolation (is the system on a network or not), high versus low bandwidth, and so on." ... A registry? Microsoft NT has one of those things. ... The third working group deals with issues of system configuration, boot up, and power management. The lines separating this group's work from that of the mobile communications working group are sometimes blurred, as evidenced by work items such as network boot specification and service location. The latter will enable devices that migrate into a new networking environment to dynamically acquire knowledge of the site and use its resources. Solutions to this problem may lie in technologies like Java's Naming and Directory Interface,9 Service Location Protocol,10 Dynamic Host Configuration Protocol,11 and Lightweight Directory Access Protocol.12 Naming requirements of platform configuration will perhaps be addressed via the Java System Database (JSD), currently being defined and slated for inclusion in a future release of the JDK. This group is defining a Java application-level power management framework consisting of four components: standardized MNC power states (full, PM active, sleep, suspend, and off), industry-standard device states, well-defined MNC power state transitions, and power management APIs. The first three components provide a homogeneous operating environment for applications. The last component provides a channel through which Java applications can learn about an MNC's power status and events and possibly influence its power management decisions. Initial revisions of the power management APIs only allow applications to query the system's power management status. Future updates will extend these capabilities. ... Does the NC sound so simple when you add all the necessary features to make it flexible enough to be practical for the typical knowledge worker? ...