c****u
发帖数: 3277 | 1 I am writing an application, the client side I am using java web start(
basically an application),
the server side I wrote an application for now. They communicate via
socket. Now I am wondering if it's a good idea to change the server side
to a servlet, still using socket.It might be more flexible for servlet
to talk to database? I am a novice to servlet now and still learning it.
The book says servlet can be of general purpose, but it's good at
handling HTTP related stuff. |
m******t
发帖数: 2416 | 2
Since you have a rich client, either SOAP or RMI would be a better choice
than servlet.
【在 c****u 的大作中提到】
: I am writing an application, the client side I am using java web start(
: basically an application),
: the server side I wrote an application for now. They communicate via
: socket. Now I am wondering if it's a good idea to change the server side
: to a servlet, still using socket.It might be more flexible for servlet
: to talk to database? I am a novice to servlet now and still learning it.
: The book says servlet can be of general purpose, but it's good at
: handling HTTP related stuff.
|
c****u
发帖数: 3277 | 3 thanks. Can you tell me why SOAP or RMI are better?
【在 m******t 的大作中提到】
:
: Since you have a rich client, either SOAP or RMI would be a better choice
: than servlet.
|
s*********n
发帖数: 13 | 4 typically a servlet is deemed as an extension of web servers.
since ur client is not a web browser, it may not be necessary to use a servlet
as ur work could be heavy in format ur information dissemination.
rmi could make ur code neat. or otherwise if u wish to extend ur application as
a web service, apache axis can offer u necessary assistance.
【在 c****u 的大作中提到】
: thanks. Can you tell me why SOAP or RMI are better?
|
c****u
发帖数: 3277 | 5 thanks.
【在 s*********n 的大作中提到】
: typically a servlet is deemed as an extension of web servers.
: since ur client is not a web browser, it may not be necessary to use a servlet
: as ur work could be heavy in format ur information dissemination.
: rmi could make ur code neat. or otherwise if u wish to extend ur application as
: a web service, apache axis can offer u necessary assistance.
|
k******e
发帖数: 10 | 6 Actually, it is a good idea to use servlet at server side. But my concern
is how web start support cookie. Without cookie, you cannot use the existed
session mechanism.
【在 c****u 的大作中提到】
: I am writing an application, the client side I am using java web start(
: basically an application),
: the server side I wrote an application for now. They communicate via
: socket. Now I am wondering if it's a good idea to change the server side
: to a servlet, still using socket.It might be more flexible for servlet
: to talk to database? I am a novice to servlet now and still learning it.
: The book says servlet can be of general purpose, but it's good at
: handling HTTP related stuff.
|
c****u
发帖数: 3277 | 7 can anyboy tell me what are the pros and cons of servlet and SOAP?
Also what's their major difference?
【在 k******e 的大作中提到】
: Actually, it is a good idea to use servlet at server side. But my concern
: is how web start support cookie. Without cookie, you cannot use the existed
: session mechanism.
|
v*x
发帖数: 1370 | 8 SOAP lets you trigger processes on a server from a remote program. You can
create classes (with methods and properties) that can be created remotely
and SOAP takes care of the details about marshalling data types, even across
heterogenous environments (most of the time!). It's sort of like RPC over
HTTP. You can write SOAP in Java, C++ or other languages.
Java Servlets are specialized Java classes that handle mostly HTTP
requests/responses, they are often used to parse or fill in forms. It is
【在 c****u 的大作中提到】
: can anyboy tell me what are the pros and cons of servlet and SOAP?
: Also what's their major difference?
|
