So this is something that has been at the back of my brain for a while
but I just haven't acted on it :(
Basically if you want to use a Turbine application with code that you
don't want connected to a web server (IE threaded Daemons, or code that
doesn't need to be connected to a web server) you are in a bad position
because if you use RunData a 3rd party could use the Servlet API
directly.
For most applications this isn't bad. I also don't think we should
remove this capability. What I would like to do is have applications
use a RunData like object that can be used without providing access to
complicated APIs (Servlet, etc)
So what I want to do is provide a ServerData object that would be
similar to RunData. The difference is that it wouldn't contain any APIs
that can change at runtime. java.lang.String being the most complex.
DynamicURI would be modified to allow ServerData as a constructor. The
constructors with RunData would stay but possibly be deprecated (I have
no opinion here).
Internally DynamicURI could operate just fine without the extra
information provided by RunData. The init() method would just work with
ServerData. The only extended information would be for a bug that was
in JServ 1.0 but this could still be provided and just wouldn't be
triggered when running in a headless env.
Thoughts?
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
"For evil to win is for good men to do nothing."
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
