Re: request/response question
Re: request/response question
- Subject: Re: request/response question
- From: arturo <email@hidden>
- Date: Wed, 18 Feb 2004 11:16:45 -0500
From: "Michael Engelhart" <email@hidden>
<rearranged slightly>
> I'm contemplating starting a large scale project in WO and while
> keeping blinders on so I don't get bogged down by trying to compare my
> J2EE experience and knowledge with WO helps in most regards, not fully
> grasping what WO is actually doing kind of gives me the willies.
I used to work with a group that never got past those willies. _That_
gave me the willies :-) And they didn't even have any J2EE experience.
> I'm more than willing to let WO be the plumber on the request-response
> stuff but I'd just feel more comfortable knowing what that plumbing is
> made up of. Or maybe I'm just being silly and I should just jump off
> the cliff.. :-)
Apple's documentation actually discusses this pretty thoroughly. Have
you looked at that?
> When a component is created for a page say and there
> are all several java methods doing different things like returning a
> dynamic row color or creating a dynamic title tag, how is WO handling
> that. Is each component's Java class instantiated for that user so
> that if say 100 users all hit the page, 100 instances of that class are
> created or are they shared instances?
There are stateful and stateless components. When you make a component
you can override "isStateless" and that tells WO whether or not to make a
pool
of them. In that case it instantiates as many as it needs at peak but they
get reused.
For stateful components it must (sort of by definition) instantiate one and
keep it
around.
_______________________________________________
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.