On Sunday 09 November 2003 11:17, [EMAIL PROTECTED] wrote: > > Maybe later. As I said, I looked at it, didn't understand it well, and > > had problem to see how to use it. > > Np don't slow down if you're gonna give me a plugin ;).
Slow down?? I need to speed up. I really want to have something running, as I have bad experiences of academic theorizing over a problem domain. Almost always leads to over design and troublesome implementations. As the chinese always says around here; "Put the money where your mouth is." > > urn:maven:http://www.ibiblio.com/apache/avalon/component/repository > Your explaination for the urn seems unnecessary. A url has a scheme and > the agent factory should know what its doing using a factory pattern. see below. > Is the [type] the switch parameter to the factory? Correct. The [type] selects the RepositoryAgentFactory and the [location] is passed to the create() method. BUT the contract explicitly dictates that the full URN can be used both at the factory select as well as the agent creation, to aid the user code, i.e. it doesn't have to bother parsing it. > You're thinking well at making the Eclipse user happy by not taking too > long and thinking ahead of the user i like that. Well, the whole reason for me to get into this is the Eclipse tool. "Use-case driven" approach/pov, remember. > > OK, this is a VERY good point. But any Query language or system typically > > requires a lot of thought to be powerful, yet reasonably easy to > > implement. Let us discuss that later/separately. > > Well questions about artifacts can be posed using an API interfaces > instead of using query language. The query language I was thinking > about was an LDAP filter which is basically like a where clause in > prefix notation: i.e. ask for all DataStore service implementation > blocks that are greater than 1.0 and can run in both Merlin and > Pheonix. > > (& (objectClass=block) (service=o.a.a.DataStore) (version>1.0) > (| (container=Merlin) (container=Phoenix) ) ) I would like to see you implement that for any type of repository, CVS for instance? This is my point regarding Query Language/API. It is easy to think that we just pass it down to the implementation (LDAP in your case), but then you don't have a semantically strong contract at the client API layer, i.e. the client can not ignore the implementation, making the whole API bad. > Let's face it a heirarchical repository with meta data is a directory. TRUE, but there are many implementations of directories. Anything from filesystems (with or without meta extensions) to virtual directories in RDBMSs. > Again realize the repo will not have Avalon specific attributes > predefined for it. We add that later as Avalon specific functionality > over the baseline. Give users generic attributes to work with > first. Exactly!! You are probably going to sleep soon ;o) and I have ~6hours of coding ahead of me, so with a bit of flow, I'll finish the Eclipse repository browser, and put up a sample repository on my web server. Cheers, Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
