Hi Akmal,

Thank you for your thoughts, this is a very useful email!  I appreciate
getting feedback of this nature. I've put some comments in:

> -extended user:
> according to what I have been experimenting so far, the extended user
> HAS to have a db table that _IS_ _NOT_ called TURBINE_USER. otherwise
> the extra columns will not be added to the db (why?). this means that we
> have to rename our TURBINE_USER to eg. EXTENDED_USER . but what if we
> don't (can't) do that?
Use the now release Hibernate based Fulcrum Security.  There is also a
Fulcrum Security adapter to hook it into the 2.3.x Turbine framework.
Avoids all the Torque nastyness...
>
> -FileItem: now the fileupload package is used but I still have problems
> compared to the home-brewed FileItem before:
>
> getName() sometimes get the whole path depending on the handling browser
> and I have to take care of that myself. I expect that to be handeld in
> the implementation.
> data.getParameters().getFileItem("file") will always return a non Null
> value even if no file is selected.
Not sure I quite understand this..  Are you saying that you would return a
File() object even if it doesn't exist?  And the getName, what are the
differing return values?
>
> -is there a good reason why TorqueUser and TorqueGroup
> do not implement Retrievable so we can use them for our intake forms.
The reason for not implementing retreivable was so TorqueUser woulnd't be
tied to Intake.  But you could just extend TorqueUser and implement
retrevable there...   However, note that in Turbine 2.4 this is all gone in
favor of Fulcrum Security.
>
> other than that we are very happy using 2.3.1 and we would be
> even happier if the Hibernate stuff could be pushed forward in
> the next release
> so we could have an example of 2.3.x with only hibernate or with
> only torque.
I agree..   The hibernate stuff will probably be in Turbine 2.4.

I'll finish up with a recommendation that you 1) look at using Turbine 2.4,
2) send in patchs for things that bother you.  Turbine is a community based
effort, and as such you can directly affect it's evolution!  I think that if
you are finding that Torque isn't working for you, and you want to use
Turbine, then Turbine 2.4 Milestone 1 will probably work for you.  I am
using it w/ Fulcrum security very successfully.  Turbine 2.4 Milestone 2
will probably be released soon, mainly updating the dependencies to the
various released Fulcrum components.

Eric Pugh


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to