rejetto forum
Software => HFS ~ HTTP File Server => Topic started by: CBB on January 14, 2007, 12:13:09 PM
-
The number of files on my server is very large, so I really need to restrict access to "file list" reference (show it not for all users), as it uses a lot of resourses.
The other related usefull feature would be to realize not only "file list" reference, but also "0day-recursive", "0week-recursive" and "0month-recursive" references (similar to http://www.kiarchive.ru/pub/ for example).
-
Can you ad a search feature to the website side of the application so that you can search the website for example to get a list of same artist in a collection of mp3's that you sharing?
-
Search feature is on to-do list, it is my most anticipated feature of hfs. You can set up a search using a program called search engine builder pro, for the time being. ID3 is also there i think, to search id3 artists maybe...
Also CBB, limiting the amount of files/ page is on the to-do list. I think this is what you are wanting... to lessen the stress of each page load on the hfs....
Please read rejetto's to-do list before posting.
:D
-
Also CBB, limiting the amount of files/ page is on the to-do list. I think this is what you are wanting... to lessen the stress of each page load on the hfs....
No, I didn't mean limiting the amount of files per page. I ment that there exists a reference named "file list" at bottom right corner of the page in browser, and if user clicks on this reference when browsing a root directory of my server - then HFS practically hangs trying to create a recursive list of several thousands of files. It uses 100% of CPU and I even can't close it in usual way, only to terminate using process manager.
On the other hand there are no problems with this reference when browsing directories with less amount of files, so I would like to make this reference available only for few users who know about this problem.
By the way, this separation of users would be much easier with user groups. I am glad that this feature is in to-do list.
-
No, I didn't mean limiting the amount of files per page. I ment that there exists a reference named "file list" at bottom right corner of the page in browser, and if user clicks on this reference when browsing a root directory of my server - then HFS practically hangs trying to create a recursive list of several thousands of files. It uses 100% of CPU and I even can't close it in usual way, only to terminate using process manager.
If you are having a problem with the File List option for your root directory, why not just remove it? End of problem. A file list of the root isn't necessary. In the [files] section of your template, remove (or comment out) this line -> <a href="~files.lst?recursive">File list</a>.
Now if you want to include the File List option for some or all of your folders, simply right click on each folder and select diff template. In the diff template add a complete [files] section (that you can copy & paste from your main template) and make sure the line -> <a href="~files.lst?recursive">File list</a> is present.
No additional feature is necessary to do this.
-
If you are having a problem with the File List option for your root directory, why not just remove it? End of problem. A file list of the root isn't necessary. In the [files] section of your template, remove (or comment out) this line -> <a href="~files.lst?recursive">File list</a>.
Now if you want to include the File List option for some or all of your folders, simply right click on each folder and select diff template. In the diff template add a complete [files] section (that you can copy & paste from your main template) and make sure the line -> <a href="~files.lst?recursive">File list</a> is present.
Thank you. I didn't pay attention on diff template option for folders. This really solves the main problem, though it is not exactly what I would like to get. May be it'll be possible to do diff template option not only for folders, but also for users? It would be ideal solution.
-
this is a problem that may need some time thinking, to find a good solution.
in the while, you may consider to remove the "?recursive" inside the template.
it's quite easy, try yourself or post for help.
-
Thank you. I didn't pay attention on diff template option for folders. This really solves the main problem
Glad to hear that problem is solved.
May be t'll be possible to do diff template option not only for folders, but also for users? It would be ideal solution.
If you are thinking of setting up a different set of folders for each of your users or if you want user groups to have access to certain folders, it can be done with the present HFS features: (I use it here)
1. Create folders.
2. Restrict access to those folders for the user or group of users.
(The users will see only the folders they have been given access to).
3. Use the diff template feature as needed for any changes you want to make.
Is this what are you trying to accomplish?
-
as you can set a diff-template to folders, he would like to set a diff-tpl to users.
is not very hard for me, but we should decide which one would have priority over the other.
-
we should decide which one would have priority over the other.
Are there any pros & cons that we should know about before the decision is made?
-
think a case of a user with diff-tpl in a folder with a diff-tpl.
what should be the resulting template in your point of view?
should only one apply? which one?
or should both apply? which first?
-
think a case of a user with diff-tpl in a folder with a diff-tpl.
what should be the resulting template in your point of view?
should only one apply? which one?
or should both apply? which first?
First of all, I have to say... I maybe wrong, but I can't see two seperate diff templates (a user diff-tpl & a folder diff-tpl in the same folder) working properly. What would be the resulting output? They might conflict in some way. I'm still not sure what the true benefit of this would be. Ok I got that out of my system. :)
Hmmm. I'm now thinking of my existing diff templates. Some serve multiple users and others serve all users. In the scenerio you suggest, I think the folder diff-tpl should have priority as it serves more than just one user and can also include global changes the admin wants to his site.
If a user diff-tpl was created, there was a reason for it. So I guess both user and folder diff-tpl should apply. You asked the question - which first? That question suggests to me that you are thinking of displaying 2 diff templates (user and folder). Somehow I think that would confuse the viewer and might not give the desired output the admin wanted. My answer to "which first" is I'm not sure. I think the best solution would be to combine the information from the user diff-tpl into the folder diff-tpl (1 resulting folder+user diff-tpl) which would still give the folder diff-tpl priority but also include the user diff-tpl information.
I'm going to have to think some more about this.
-
maybe, since user-diff-tpl should have a dialog itself, we may let the user decide the priority.
-
If you are thinking of setting up a different set of folders for each of your users or if you want user groups to have access to certain folders, it can be done with the present HFS features: (I use it here)
1. Create folders.
2. Restrict access to those folders for the user or group of users.
(The users will see only the folders they have been given access to).
3. Use the diff template feature as needed for any changes you want to make.
Is this what are you trying to accomplish?
Not exactly, I want to have diff. templates for different users in the same folders, but now I've found the way to simulate user-diff-tpl using folder-diff-tpl. To do this I create in root folder several entries for each shared folder on my server, then for each entry choose diff.template option, and then give each user access only to one of similar entries. Now each user browses the same set of folders, but with his own template. A bit bulky but it works.
-
think a case of a user with diff-tpl in a folder with a diff-tpl.
what should be the resulting template in your point of view?
should only one apply? which one?
or should both apply? which first?
I'd say both should be applied and user diff-tpl should be last (thus it will have higher priority). Though it may be an option of course.
-
If you are thinking of setting up a different set of folders for each of your users or if you want user groups to have access to certain folders, it can be done with the present HFS features: (I use it here)
1. Create folders.
2. Restrict access to those folders for the user or group of users.
(The users will see only the folders they have been given access to).
3. Use the diff template feature as needed for any changes you want to make.
Is this what are you trying to accomplish?
Not exactly, I want to have diff. templates for different users in the same folders, but now I've found the way to simulate user-diff-tpl using folder-diff-tpl.
That is what I was suggesting in my comments above your's. Maybe I could have been a bit clearer. Anyway, I see that you are playing around with the options now and making HFS do what you want it to do with the features that are presently available. Good job.
-
If you are thinking of setting up a different set of folders for each of your users or if you want user groups to have access to certain folders...
Not exactly, I want to have diff. templates for different users in the same folders...
That is what I was suggesting in my comments above your's. Maybe I could have been a bit clearer.
I beware that maybe I should explain a bit clearer. From my point of view the main difference in our proposals is that I get diff templates for different users in the same folder (not in different folders!), and to get this effect I create in VFS several instances of the same real folder (for example, \music1 , \music2 and \music3 instances in VFS for the same E:\Music\ directory on hard disk) and then apply diff template option and access restrictions for different instances of the same folder (not for different real folders).
-
maybe, since user-diff-tpl should have a dialog itself, we may let the user decide the priority.
That might be a good idea. Let the user decide the priority. How would a user do that? I just assumed that would have to be decided upon at the server level.
Like folder-diff-tpl, user-diff-tpl should be an OPTIONAL feature.
-
sure, a server-side option