Re: WebObjects vs. Servlet
Re: WebObjects vs. Servlet
- Subject: Re: WebObjects vs. Servlet
- From: Hsu <email@hidden>
- Date: Tue, 28 Oct 2003 20:02:22 -0800
I'm not sure I understand... WebObjects is an application server. All
it does is "sits and listens". You connect on whatever port it's
running on, send it some data, and it processes that and (optionally)
sends a response. That's what a server does.
Karl
On Oct 28, 2003, at 3:56 PM, Bob McCormick wrote:
Have another question here that has me wondering if this is best
handled by WO or a Servlet.
If I have a server sitting there watching a port and waiting for a
client to connect and then start sending images (medical DICOM images
from a Scanner), is WO capable of in effect acting as a daemon or
service that simple sits and listens? I'm not thinking that
WebServices is what needs to be the broker here as basically we're
just sucking up data, updating the database for file location; but hey
maybe it is. Dunno as I haven't had the opportunity to play with
WebServices much yet.
I know that I've seen pure servlets running on TomCat to act like a
daemon that just runs and fires up whenever a connection is made on a
specified port. Now, I'm wondering if keeping all source for such a
utility in WO only makes sense or can even be done.
Appreciate any thoughts on this one.
Thanks....Bob
Bob McCormick
XebraTech
(805) 302-3359
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
--
What nonsense, this saying of beauty being only skin deep. What else
would you want? An adorable pancreas?
Homepage:
http://homepage.mac.com/khsu/index.html
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.