Most of the ND user’s must make some decision in the next few months in regard
to what
they are going to do with ND 5.02 and iAS 6.0 (iPlanet) or look for some other
application servers.
I am going to make a few posting here to address some of the issues.
Again as team ND member I only speak for myself and not ND or Sun.
There are two main platforms you can use to do web applications.
(I do not use the term standard because they are controlled by one company)
One is the J2EE platform and the other is the ASP platform.
The Microsoft ASP platform is more established with gui development tools.
It is the market leader for web applications, which do not have a lot of hits.
Microsoft claims they have a very robust ASP solution running under window 2000.
It will take at least 4 months to tell whether that is true or not.
I have followed the ASP technology since 1996 using interDev 1.0.
Microsoft’s approach in InterDev is similar to VB where it excels in the GUI
side.
If what you need on the GUI side can be done using the objects(design time controls)
InterDev provides you
Then it is relatively easy to do.
If you have to do your own gui implementation then it is quite messy.
One performance issue that most people do not pay attention to is that the sample
bench mark
Microsoft uses for performance analysis do not use any design time controls (GUI
objects).
They just use plain HTML. (This is equivalent to JSP under J2EE)
You pay a heavy price if you use the GIU objects but your development time will be
reduced.
May be I am bias towards ND, I still like the ND studio‘s handling of the gui
objects.
It gives me the ease of use plus if I need to do extra things for my gui object I can
do that too.
The only major problem I have is the fact that ND uses xxxx(yyyy) as the name of the
image button
and I cannot reference that button in my client side scripts under netscape browsers.
The J2EE platform is relatively new (The final spec was released last Friday)
but contain many components which have been in Java for many years.
Since it is a more recently developed platform, theoretically it is a better platform.
>From the front end side you can either use JSP or servelets.
JSP is simular to ASP and it is compiled into servelets.
Currently it does not have the same development tool as Microsoft have.
One major objective for the J2EE platform in theory is that you should be able to
develop
Your web application and run it on any 100% compliant J2EE application server.
If all vendors do this then this would be great.
Every vendor except Microsoft probably is going to support J2EE.
The only question is whether they are going to be 100%.
One potential problem is custom classes that the vendor provides.
If you use them you will not going to be able to move your applications to another
vendor.
My prediction is that within 6 months, most of the "new" web application development
will use either ASP or J2EE.
Some special system may still use C++ for better performance.
Most of the low end application will use ASP and most of the high end applications
will use J2EE.
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
