On Mon, Jul 22, 2013 at 1:30 PM, Eduardo Morras <emorr...@yahoo.es> wrote:
> Xcb uses an async mechanism, it creates a cookie, sends it and data to the > external code, keep working. External code calls xcb, sends the cookie with > the answer. Data and cookie can be exchanged through sql table. > Then it starts looking like a message queue, and i personally have no intention of seeing fossil grow into such a creature. > > To be clear, i often use the words hook/plugin/trigger interchangeably. > > They are different. A hook is capability we add to a function, as a > anonymous function pointer. This way we can "hook" the any function to > program flow, changing it. A plugin is a module that adds capabilities to > program. For example Sqlite3 has plugin mechanism to add external > aggreagate calculations. A trigger is code that executes other code when > some conditions met. > Yes - didn't mean to imply that my (mis)use of the terms was correct ;). > So the difference is that a hook allows a plugin work when the trigger > wants. > Agreed. > That's why I said I confused user with role. The role owns the files, not > the user. Currently, a user without wiki role capabilities can't modify the > wiki files. > Yes he can - he simply needs to clone it. At that point any access rights fly out the window. > Similar, a C developer role can modify /src dir but not /documentation or > /sql, the DBA role can change /sql but not /src and similar. Role info is > already exchanged in pull/push/sync, user info not. So in your scenary, a > user can get the role capabilities and access them. > So what happens when i (as a wiki editor) make a change to src/foo.c, commit it to my local copy (because locally i have admin access) and then try to push? i can't, and my repo then gets (permanently) out of sync. i don't think this model is possible in a DVCS. > The problem is that a user is admin of his own repository file and can set > whatever s/he wants and access everything. A global dvcs role and user data > can solve this, not allowing this user make changes in public branches or > trunk directories of central repo (or other users repos) if s/he has no > privileges to do so. > Once i clone it, the central repository has NO say-so in what i can and cannot check out. It can only control what i check IN, or (more correctly), what i try to push to the central server. If it will not let me push the changes i have already committed to my local repo then i have a serious problem. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
