Messages

1

HFS ~ HTTP File Server / Re: Queues

« on: April 22, 2009, 07:50:55 PM »

Actually it does exist in HFS. It called "Max simultaneous downloads from single address"=1  and  "Max simultaneous addresses"=100. This way you will get almost exactly same behavior: 100 users will be able to download single file at the time.

This isn't a queue .. its free for all. What I need to be able to do is setup so that server has the ability to send 5 simultaneous files at the same time. If a user a requests a file and its already sending 5 files ... instead of saying "No you can't, please try later", it adds them to a queue. Now when one of those 5 simultaneous sends finishes, the person waiting gets sent their file.

2

HFS ~ HTTP File Server / Re: Queues

« on: April 22, 2009, 07:27:43 AM »

This is what i've experienced so far <snip>

Cheers for the information really useful. I think I'll have to play with the simultaneous downloads during the event to try and best utilize the bandwidth.

3

HFS ~ HTTP File Server / Re: Queues

« on: April 21, 2009, 09:18:04 PM »

Hfs do not can work in the way you want it, on the other hand it is possible to select several files and to download them in the form of archive TAR.

Is'nt it  rejetto?

Yes but serving 100 peoples file sequentially is a lot quicker than serving 100 peoples files simultaneously. (provided the disk isn't too badly fragmented).

i'm sorry, but such feature is not present in HFS.

ah ok .. thanks once again.

For background I was intending ( and may still do so) using the software at a LAN party to serve file patches ( these range from a few mb to a few gb in size). There are normally 250+ people at the LAN, obviously this volume of simultaneous requests on a file server will kill a box.

4

HFS ~ HTTP File Server / Re: Queues

« on: April 21, 2009, 08:48:04 PM »

Hi. thanks for the welcome and the quick reply.

Yes nearly all file serving websites do what I'm asking, fileplanet and fileshack both implement a queueing system. The way they work ( and the system I half wrote worked) is when a file is requested its added into a queue on the server. Periodically the client ( in this case the web browser) polls the server to see if its turn is up. If not the page refreshes displaying the new position, if it is the turn then it sends the file in the usual manner.

Of course ( and this is the bit I never finished) the server maintains a list of when it last heard from the client and removes it if its not heard from it in a while. This takes care of when a client navigates away from a page. ( actually the two I mentioned both throw up a 2nd window to poll the server from).

5

HFS ~ HTTP File Server / Queues

« on: April 21, 2009, 03:10:28 PM »

Fantastic product by the way, been looking for something like this for a while ( even started writing my own a while in php but never got around to finishing it).

I'm hoping I'm being stupid, but does the file server support queues ? by this I mean that the server can only support 1 simultaneous downloads but 10 users could request a file and as the sender frees up it the next file in the queue to the user that requested it.