Ok,
I'm going through all the emails and compiling a set of notes of things that
I see. Please correct me if I am wrong as I have 130+ emails to try to sort
out and I may have missed some of the results of the threads. This email is
going to be worded more how I want to see things. Again, please correct me
if I'm wrong and also replace to this and tell me what the final decision
was.
Documentation:
A generated form of the documentation should live within the turbine/docs
directory. Not in its own CVS tree/module. This is to stay consistent with
the current way of doing things which I don't see as needing to change. It
is also how other systems are based such as tigris.org so I really don't
want to change it since we will move to a Helm based system someday.
Using a turbine/xdocs/ directory for the XML source is fine with me.
Since we are now processing the doc's to create them. Documentation should
be able to be generated from an Ant task. I want to be able to do this:
./build-turbine.sh docs
The turbine/docs/ directory is what is checked out of CVS and then placed on
java.apache.org/turbine/. Right now, this is a manual process and will
continue that way for a while. Call it security paranoia.
TODO:
The TODO document needs to be updated. I saw one note from Manik about an
old TODO item (update email stuff to use ECS...when in fact, we should use
WM now).
CLOBS:
If you want the Peer model to support it, you don't have to use Village. Go
with straight JDBC for the underlying code.
TORQUE:
Multiple index/unique issue brought up by fanyun. Has it been resolved?
Jason, can you make this happen please?
SCHEDULER:
John Thorhauer suggested fixing the scheduler to do 1 second granularity.
I'm +1 on that. Go ahead and break stuff.
SEARCHING:
It would be nice to have an interface or two that defines what a search
engine is as well as a few implementations of those interfaces. If you look
in Jyve, there is basic %foo% style searching implemented in there. Doing
something like that that is cleaner would be *really* nice to have.
INFINITE REDIRECT:
The issue is that if a session has not been assigned to a user, then they
are redirected to the "screen.homepage". The problem is that it is easily
possible to get caught in an infinite redirect loop because you could
redirect to the same URL over and over again and could be a DOS
(denial-of-service) attack against Turbine. So, if you have suggestions on
how to make this code more reliable, I would appreciate it, but I am -1 on
removing it.
DAVE's SAMPLE APPLICATION:
+1 on including it in the TDK. I think that Fanyun has a point about being
more complex, except that in reality, if it was TOO complex, then it would
confuse people. I think that even Jyve was to complex for some people.
Essentially, I think that Turbine will always have the problem of being a
large chunk of useful code and instead of focusing on providing examples, we
can only focus on providing documentation.
UNIQUE IDENTIFIER (Rafal):
Uh. Why is this exactly needed? Seems like unnecessary overhead as computing
a MD5 hash is expensive. Could you please give more details about this? I am
_very_ wary of adding code to Turbine.java...so anything added there *must*
be under extremely defined purposes and *must not* be something that could
be implemented elsewhere. If anything, this should be optionally defined in
the TurbineResources.properties file as a boolean (default: false) so that I
can turn it off.
FILE UPLOAD:
Do not worry about relying on the O'Reilly file upload code. I work with
Jason Hunter, the author of the code. It really isn't an issue as I can just
buy him a beer to resolve things. :-) Rafal, go ahead and check in your
changes. I appreciate that you like to post them on your site first, but
most people don't have the time to download them and check them out first. I
would much rather see your code in CVS and read the commit logs and then
complain about it later. :-) Luckily, your commits are 99.99% great so there
are few complaints I think.
LDAP:
+1. Implement it as a service.
thanks,
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
