[ 
https://issues.apache.org/jira/browse/JAMES-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180445#comment-17180445
 ] 

Ioan Eugen Stan commented on JAMES-3360:
----------------------------------------

I'm not a native speaker so take this with a bit of salt :).

The change is mostly wording as you say and IMO not something to spend much 
time on it .

As long as it's documented how it works we can name it however we want.

I think the name comes from the repository pattern which is not far from what 
it does: [https://deviq.com/repository-pattern/]

Directory is more of a read-only thing (not necessarily) while repository is 
read/write.

I think in James we can have both types, depending on who maintains the user 
list: James (we have rw or another system - we will have just read access most 
likely)

https://www.merriam-webster.com/dictionary/repository

 

> Change "User Repository" to "User Directory"
> --------------------------------------------
>
>                 Key: JAMES-3360
>                 URL: https://issues.apache.org/jira/browse/JAMES-3360
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: David Leangen
>            Priority: Major
>
> I wonder if there isn't a wording problem here.
> I understand that the idea is to have a place to store user data. However, 
> the naming looks at the problem from a purely technical point of view. A 
> "Repository" by definition is a place to "put" something. For example, in the 
> real world, a document repository is an actual place to put documents.
> The wording suggests that we have some place where we put people, which seems 
> very strange to me if we correspond the idea to the real world. It creates a 
> very strange mental model for me.
> I think the concept that should be modeled here is more along the lines of a 
> "Directory". We have a kind of index that gives useful information about how 
> to locate users. It is not a place where we take people and lock them up. 
> Rather, it is a list of information about people. Does that make sense?
> [Here is a 
> definition|https://dictionary.cambridge.org/dictionary/english/directory] we 
> could use:
> {quote}a list of telephone numbers, names, addresses, or other information
> {quote}
> Note that if the Repository is never exposed to anybody except implementors, 
> and it really is just a place to put data, then this issue would not bother 
> me. However, it is my understanding from writing the new documents that this 
> concept is actually exposed, so I think the concept needs to be fixed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

Reply via email to