rejetto forum
Software => HFS ~ HTTP File Server => Topic started by: rejetto on May 12, 2012, 11:00:08 AM
-
good news everyone!
the project is somewhere around 1% now :)
I could made some tests, and i want you to know that this brand new version (tho at an early stage) is already showing some BIG advantages brought by the new technology it is built upon:
- unicode file names supported
- much easier: no more need to choose between real and virtual folders, just one powerful folder
- administration accessible over the net
- max throughput triplicated *
Not bad for a 1%, is it?
Now i need to call you to arms!
If i do this project alone it won't hit 100% before 1 or 2 more years.
I'm searching for tough javascript programmers willing to help.
Anyone?
*the measuring has been done by downloading with wget in local. Version 2.3 reached 35MB/s while version 3 sported a glorious 126MB/s. No improvement is expected for slow internet connections: if you already are hitting the limit of your own internet connection don't dream about overcoming it. I cannot yet tell what will be the real gain for fast networks, we'll see.
-
JavaScript@_@
I am only good in ruby :P
Not to say I got no idea how to do OO with JS~~
Just wanna know what you use to build/write front-end and back-end
If I still got free time after going to work and maintaining my Firefox extension I will come :-\
-
That's not good news, that's GREAT news! No JS or even programming knowledge with me at all, I'm afraid... :(
-
Cool, I hope you can find some people qualified enough for the job. By JavaScript I'll assume you'll be wanting help with the default web interfaces for it (jQuery, jQuery UI etc?). Unfortunately I just haven't got the time lately for open source projects. Have been saving to move out etc. I think Richard is in the same boat.
Has HFS had a stable release as it is now, since you are writing it from scratch?
-
By JavaScript I'll assume you'll be wanting help with the default web interfaces for it (jQuery, jQuery UI etc?).
yes and no. Even the server-side is made in javascript :)
http://nodejs.org/
there will be for sure 3 distinct part:
server (core and services)
front-end (to browse the folders)
back-end (for administration)
Has HFS had a stable release as it is now, since you are writing it from scratch?
are you talking about version 2 or 3?
no news for 2, and not even alpha version for 3 (i said it's 1%)
nevertheless (about 3) those advantages i reported are already in that first 1%
-
So you're not putting PHP or even macros into version 3?
-
So you're not putting PHP or even macros into version 3?
i didn't take yet the time to explore this matter.
Point of it all is having a server side scripting: that's what macros and PHP are.
The official server scripting will be javascript, that will blend nicely and very fast because things will just become part of HFS, not just executed by an internal interpreter as we do now for macros. I don't personally plan to work on getting macros on HFS 3.
PHP, as other languages, should come thanks to CGI: a standard way to run different things inside the webserver. Apparently CGI is readily available (https://github.com/TooTallNate/node-cgi), but didn't try it yet. Being at a 1% and still alone (with a full-time job) it all goes very slow.
I didn't design how "templates" will be. I'm now trying to get a sort of template working, then we'll see how to get something cool to customize.
Interested programmers with plenty of free time can try to get a preview running. :) First step is installing node.js and have it working, then you can come back to me.
-
good news everyone!
the project is somewhere around 1% now :)
- max throughput triplicated *
Not bad for a 1%, is it?
*the measuring has been done by downloading with wget in local. Version 2.3 reached 35MB/s while version 3 sported a glorious 126MB/s. No improvement is expected for slow internet connections: if you already are hitting the limit of your own internet connection don't dream about overcoming it. I cannot yet tell what will be the real gain for fast networks, we'll see.
Will you release an alpha?
-
good news everyone!
the project is somewhere around 1% now :)
I could made some tests, and i want you to know that this brand new version (tho at an early stage) is already showing some BIG advantages brought by the new technology it is built upon:
- unicode file names supported
- much easier: no more need to choose between real and virtual folders, just one powerful folder
- administration accessible over the net
- max throughput triplicated *
Not bad for a 1%, is it?
Now i need to call you to arms!
If i do this project alone it won't hit 100% before 1 or 2 more years.
I'm searching for tough javascript programmers willing to help.
Anyone?
*the measuring has been done by downloading with wget in local. Version 2.3 reached 35MB/s while version 3 sported a glorious 126MB/s. No improvement is expected for slow internet connections: if you already are hitting the limit of your own internet connection don't dream about overcoming it. I cannot yet tell what will be the real gain for fast networks, we'll see.
IMO, if let it as Open Source and let everyone to commit at github might help.
-
Q moved to http://www.rejetto.com/forum/index.php/topic,10482.0.html
Will you release an alpha?
at the moment it's not even useful, it's more a technology demostration than an alpha.
Anyway, yes, i mean to publish something in the next days, because i want to explore distribution/deploying methods.
It all depends on the amount of time i find to work on it.
-
IMO, if let it as Open Source and let everyone to commit at github might help.
version 3 will be open source as well, yes.
i meant to use sourceforge, since it all started there.
Anyway i know github is the "standard" for Node projects. I'll consider that.
-
I think if you want more people to help,
using GitHub is better since people can fork (copy the whole repo),
make changes, commit, then start a pull request (merge)
Better than sending a patch...
Never worked on SourceForge. How do people collaborate there?
-
i switched to github, mainly because of the GIT system.
Never worked on SourceForge. How do people collaborate there?
they use SVN, very close but not as cool as GIT