I strongly suspect that I will regret asking this, but it is an area where feedback may be useful.
I have been working on getting the secure server version of Bob ready for an actual release where we can host wikis that have Bobs features and there need to be proper access controls so that uploaded files are only accessible with the correct credentials. This leads to things that work fine on the server but may be a bit strange on a local version of Bob. Currently on the local version of Bob files can be served from a single folder and its sub-folders and the same files are available in every wiki. This doesn't give the desired granularity for access control so on the server version I am making it so that there is a globally accessible (assuming you have the correct permissions) pool of files which act the same as the local version of Bob, but then each wiki can also have files that have the same access controls as that wiki does. So in effect there will be a pool of globally accessible files and then files that are accessible on individual wikis. The problems come from how you address the files. Currently on the local version you use a uri that starts with /files/ and then you can put in the path to the specific file you want. My plan is to make it so that if you have a wiki called MyWiki than files specific to that wiki would be accessible using a url prefixed with /files/MyWiki/ and the files would be stored in the files subfolder of the wiki folder. This is there there are potential problems. In the folder where you have the globally accessible files any subfolder that shares a name with an existing wiki will not be accessible because the url would be the same as the one that points to files for that wiki. A wiki named Foo would similarly not be able to have any files in a folder Bar if there was a wiki on Foo/Bar These aren't significant problems on the server because due to the interface there isn't going to be much of a chance to have sub-folders, but when running Bob locally it may come up. I don't have much in the way of an alternate suggestions other than just getting rid of the globally accessible files, but that seems like a poor choice. Would using this be a problem for anyone, and if so why? or let me know if you have a constructive suggestion or opinion. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2775da22-80a9-4074-9e05-877f3e09d3f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
