I just started looking at this. Has anyone gone through a process to
enforce/engage/initiate the use of thread safe coding techniques?
This is based on the assumption that we desire/need to allow the
concurrent running of web agents. I say assumption because I had gone
through a period of time where we had numerous issues with semaphore
locks (almost all caused by HTTP agents) that I would typify as
coding/logic problems. Most of those have been cleaned up. However, we
just had another 'blip' and conceptually this bothers me. If we have a
web agent that misbehaves (for whatever reason) it has the ability to
impact all other web agents/applications.
Our applications are 99% Domino. We only have a few functions that are
Notes based. When the HTTP side goes black or brown I get all kinds of
noise about the server locking up. It has taking some convincing to get
some developers to step up and clean up some questionable practices.
However, it has me thinking architecturally about the risk of being
synchronous and then I also have the nay-sayers who can't believe that
Domino has this single thread risk.
It would seem that if you don't have these coding problems or an over
busy server the gain may not be great. It also seems that this is not
an easy to solve and manage solution based on what I'm reading.
Tools?
Practices?
Experience?
Is the pain worth the gain?
Michael Crump
Manager, Computing Services
Verallia
SGCI
1509 S. Macedonia Ave.
Muncie, IN 47302
765.741.7696
765.741.7012 f
www.verallia.com <
http://www.verallia.com/>
Stupidity
Quitters never win, winners never quit, but those who never win AND
never quit are idiots.
This email and its attachments may be confidential and are intended
solely for the use of the individual to whom it is addressed. Any view
or opinions expressed are solely those of the author and do not
necessarily represent those of Saint-Gobain. If you are not the
intended recipient of this email and its attachments, you must take no
action based upon them, nor must you copy or show them to anyone.
Please contact the sender if you believe you have received this email in
error.
midrange.com
