Re: request/response question
Re: request/response question
- Subject: Re: request/response question
- From: Karl <email@hidden>
- Date: Thu, 19 Feb 2004 01:03:01 -0500
Hi,
A WOComponent contains a reference to a single graph of WOElements
(either WOComponents or Dynamic Elements). When you drop controls onto
a WO Form using WOBuilder, these controls are usually Dynamic Elements.
Only one instance of a Dynamic Element is instantiated to serve ALL
requests for a particular WOComponent (ie. a WO Form or Page).
By definition, Dynamic Elements are stateless and have to be threadsafe
since they are expected to be able to handle concurrent requests. They
obtain their bindings using WOContext and associations at runtime.
I wouldn't worry too much about any overhead. WO is very efficient at
reusing its components.
Karl
On Feb 18, 2004, at 10:03 AM, Michael Engelhart wrote:
Hi -
I have what is probably an obvious question but I can't seem to wrap
my head around it. 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? I'm noticing
that there aren't synchronized methods mentioned much in the
documentation and books I have regarding how to build simple
components and am just trying to understand what happens in the
request-response lifecycle.
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'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.. :-)
THanks for any pointers or advice.
Mike Engelhart
_______________________________________________
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.
_______________________________________________
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.