330 Java Tips.pdf - FTP Server

General Java Questions I
The JSP/Servlet model is more geared toward distributed n-tier applications where
there is at least logical, and possibly physical, separation of model, view, and
controller functions. It is more complex than PHP, but also more scalable, and
well-written Java apps may be a great deal more maintainable because of the
separation of logical tiers.
They're both nice tools, and I use both, but I don't think either one is going to kill the
other anytime soon.
--
Joe
Q: My question is : is JSP as powerful as servlet?
I heard that JSP will eventually compile into servlet class file.
One thing can be done by servlet, can it be done by JSP too? In terms of http.
Answer: Everything a servlet does can be done in JSP and vice versa. Good
programming practice (you will see some articles over the last year in JavaPro)
dictates to combine servlets and JSP in any significant web application.
JSP should be mainly HTML (or XML, or WML or whateverML) with little Java inside.
Servlets should be Java with few or not at all lines like this:
out.println( "" );
out.printlb( "" );
This creates a more or less clean separation between presentation (JSP) and
business logic (servlet).
Java beans also have a role in this. I strongly recommend the JavaPro articles or
whatever text on the MVC model you can find.
-eugene
aresteanu
Q: I'm just starting to learn Java on my own. Should I first learn AWT or should I
jump directly into the Swing of things?
Answer: Will you be wanting to code applets that are easy for anyone to run in their
browser? If so, you'll probably have to go with the AWT for now.
The AWT isn't so bad, but Swing makes a lot of things much easier, so if you want to
ship native-code applications or suchlike then I'd go with Swing. I still use the AWT,
but I find myself having to code a lot of 'standard' things myself.
--
Mark
Swing make things easier but IE doesn't support it.
Q: I can't manipulate inodes on my linux box ... in fact I can't even get real info
about a file! Java is a bad hack and is for kids who aren't sharp enough to do C++.
Answer: Think of Java in the same terms as COBOL and VB, and you've got the right
idea. Start thinking of it as a replacement for C++ and you're on the wrong track.
Don't expect this portable language to be a tool for low-level coding with hooks into
the OS and hardware internals. It just wasn't designed for that. It's an excellent
*applications* language, not a *systems* language like C or assembler.
On the other hand, if any pesky Java programmers tell you that C++ is dead and that
Java can do everything C++ does, and more, you may howl with laugher and tell
them to eat their JVM.
file:///F|/350_t/350_tips/general_java-I.htm (3 of 31) [2002-02-27 21:18:17]