Richard Unger wrote:
Hi!Right on.
That was me talking about the LDAP store. We had a discussion about the user storage etc in slide... I think we settled on that I had to read up on JAAS and then we'd continue or something like that.
This kind of question clearly ties into that discussion though. Clearly the
principal should be available to the stores, as some people might need
authentication when writing to a DB, etc, I think that was Mike's point, right?
I guess it is usual for Servers to have a 'Context' encapsulating things likeThe ThreadLocal that is used to retain the Transaction Xid is availble 'everywhere' and is unique by thread invocation.
the principal, etc... I think the SlideToken represents some of these ideas, it
just isn't visible everywhere is the problem.
So....if Slide had a SlideLocal extends ThreadLocal subclass and that had a Hashtable slideTable, then adding it to only a couple of places would yield a wealth of accessibility through something like
AbstractWebdavMethod...
run(...)
...
+ slideTable.put("AbstractWebdavMethod", this)would save the reference back to the current instance of AbstractWebdavMethod with its SlideToken and request, and response members.
Then instead of
AbstractTxFileStoreService... protected ThreadLocal activeTransactionBranch = new ThreadLocal();
it would change to
protected SlideLocal activeTransactionBranch = new SlideLocal();
and all the activeTransactionBranch.set(TxId) and activeTransactionBranch.get()
would NOT change, and would behave as it does now, but elsewhere a
SlideLocal slideLocal = new SlideLocal() Hashtable slideTable = slideLocal.getSlideTable()
would get that Hashtable with the object references where you could get the SlideToken, request, response, etc.
This wouldn't require very many changes and would have negligable impact but would expose the context to the Stores who already have access to the activeTransactionBranch.
Ollie
I also think making these changes to all parts of slide is something that should wait for a 2.1 release, perhaps along with a better user storage concept...
Richie
Quoting Oliver Zeigermann <[EMAIL PROTECTED]>:
Mike Oliver wrote:
One of the features of Slide on the web site since 1.0.16 is the following, " It can integrate and manage data stored within external repositories, requiring only small abstraction layers to be written for each repository." If I want to use Livelink, Lotus Notes, Documentum, FileNet, PcDocs, SAP, and the list goes on as an "external repository" THAT repository will undoubtedly want to know "who stores content". Are not the Stores this "abstraction layer" the web site still refers to?Hmmmm. I am certainly not a security expert, but I understand the SecurityStore together with Security (package org.apache.slide.security) is in charge of identifying users and rights. Haven't I heard somebody talk about a LDAP implementation of SecurityStore? Can not find it any more...
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------
This mail sent through the ungerground webmail system
--------------------------------------------------------------------- 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]
