Hello Frederick,
> Will Moab, JVM and the JAVA environment it enable be capable of
> writing data output - separate from GUI display - to disk?
Yes ... this can be accomplished! Depending on the type of data, the Java applet, or application, could be storing information in the directory as objects or attributes, and can also communicate to Java classes on the server which could provide file storage capabilities.
> The NT shops I touch base with have been told by MS that JAVA is
> DOA because it will never be able to write data output to disk.
This is not a technically accurate statement ... by default, the Java 'sandbox' does not allow a Java app to write to disk ... but the newest SDK is supposed to allow for this. Also, if any local classes have been installed, or if a network service is accessible which allows for this ...
I know that Microsoft does not like the idea of a platform which does not require huge amounts of storage. If you have no local storage then you certainly can not install any Windows product.
The more that I look at networking, I would really like to see all data get written to network storage, instead of local storage, because then it is accessible to me from *any* workstation that I can get to.
> My guess is that MS is planning to make sure it's NT platform will
> not support full JAVA data disk writing functionality. They are
> putting up barriers along all fronts to impede JAVA's progress.
Yep ... they want you to have to have a lot of local storage for the OS to be installed.
> From my vantage point, if MS is playing this game, NOS vendors -
> ie. Novell - should be all over the opportunity this presents.
We are thoroughly involved in JNDI, which is the Java Naming and Directory Interface, to allow the directory to be used for storage. We are also working to expose all of the other NetWare services to Java apps.
> I regard JAVA as a breakthrough, but all I've seen are the display
> benefits. I am less clear about data writing, printing, etc.
Data storage is an issue ... but one that is being solved. Printing is another very good example ... it requires the ability to access a print queue or print device ... I'm guessing that our direction will be to try and support network access to print queues.
> All Novell investors are banking on Schmidt's ability to capitalize
> on these huge gaps. A JAVA-enabled NOS that takes control over data
> writing from NT is a core requirement for Novell to succeed.
We need to make sure that Java apps can write data from NT, and from all other platforms that Java supports. And we are working in that direction. I will have to look a little deeper to determine the exact status.
> Appreciate your contributions.
More than glad to help!
Scott C. Lemon |
