Hi Thomas,
regarding XSLT Service
+) can you sent your current patch (again)?
+) do you also have test cases for it - there are no tests in the code
base .... :-(
regarding Security Service
+) my personal opinion : I'm not proposing to replace the Security
Service since it is a critical piece of functionality, it is quite huge
and I'm not familiar with code base anyway
Cheers,
Siegfried Goeschl
Thomas Vandahl wrote:
Eric Pugh wrote:
Not deprecated at all
[...]
* security (but maybe should be?)
I don't think so. The supported backends of the Turbine Security
Service and the Fulcrum Security Service differ a lot. I guess that
several people (including me) use the "default" security based on
Torque which is not available in Fulcrum (well, actually it could be,
if I only got time to get it completed) LDAP is another issue.
I would also be interested in feedback (and help!) on converting the
remaining services to Fulcrum/Avalon.
Do you think that particulary the Fulcrum security service is ready
for prime time? I remember seeing a couple of
"this-needs-to-be-completed-some-day"-kind of comments in the code. I
would like to offer help in that area, especially as I have a port of
the Torque-backend "almost" ready. I only want to make sure that the
base I built upon is stable.
2) were there any commits regarding the deprecated Turbine services
not being reflected in the Fulcrum services?
I made some extensions to the XSLT-service which are not in the
Fulcrum code (yet). XSLT is not deprecated, however.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
