> This context root is used to determine whether a request will be
handled
> by the application server or just by the web server.
OK, thanks for the link. That is starting to make sense.
I still don't see how your context root mappings could force a request
to go to a certain instance, since the context root us supposed to
determine the application within the instance which will handle the
request. ("The J2EE application server uses this initial portion of the
URL ... to determine which web application services an incoming
request.")
Of course, I'm not quite sure what multiple applications within one
instance would look like... It seems to me all we are talking about is
a subdirectory.
Is the term "application" and "instance" interchangeable?
Am I correct when I assume one instance of CF could have multiple
applications?
How exactly are they defining the term "application"?
I guess one thing that is confusing me is that it doesn't seem that my
ColdFusion instance has a clue where the actual CFM files for my
"application" reside. Nowhere in the setup for my new instance do I
specify that. I tell IIS in the "Local Path" setting under the "home
directory" tab where to go to find the CFM files. So, when I request a
page in my browser, IIS goes and finds that file in the local path and
then via its file type determines that it needs to be handled by the
application server. Then IIS contacts the cluster through the web
server connector. The cluster then chooses the next instance in the
round robin to handle the request. Now at what point in the process
does the context root come into play? I assume the web server and its
connectors are not aware of the context root. Of course, your quote
above says that "The context root is used to determine whether a request
will be handled by the application server or just by the web server".
In that case the web serer would need to be aware of the context root.
Man, this is driving me nuts. The harder I try to think about it, the
more questions I come up with and the more my brain hurts. :)
======
>You could handle all charting requests on a single server, or specify
the
>URL for one server rather than the uURL for the cluster when visiting a
> page that will let the user generate a chart.
I guess that would work, but it sure seems lame. We use cfchart all
over our site interspersed throughout the pages. The pages which
display the charts are still part of the rest of the application and
need to be part of the cluster so they can share all the needed session
info.
How have other people dealt with this in real life?
What about my sticky sage question?
~Brad
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Create Web Applications With ColdFusion MX7 & Flex 2.
Build powerful, scalable RIAs. Free Trial
http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJS
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:273690
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
