Summary: | request for "weborf" package | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Salvo 'LtWorf' Tomaselli <tiposchi> |
Component: | Current packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | mjo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://ltworf.github.io/weborf/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Salvo 'LtWorf' Tomaselli
2010-02-22 13:54:42 UTC
Does this do anything that $ python2 -m SimpleHTTPServer or $ python3 -m http.server doesn't do? Just wondering if we still need to consider adding this package! Wow… after 6 years this hasn't been triaged yet? This is the new website of the project http://ltworf.github.io/weborf/ It comes with a GUI for easy directory sharing, that opens external ports from inside NAT. The server supports being started by xinetd, supports CGI, partial download, and webdav, so you can use it to mount directories with davfs remotely. When doing so has a (so far unique) cache for dynamic content that greatly reduces the CPU load, because it avoids re-creating all the XML over and over (clients tend to send the same request tens of times). It can also be used to send over a whole directory as .tar file, when started with the appropriate parameter. Best. (In reply to Salvo 'LtWorf' Tomaselli from comment #2) > Wow… after 6 years this hasn't been triaged yet? Well I just realized that we have about 4,000 bugs sitting around assigned to no one. I'm trying to go through and figure out which ones are obsolete to cut down the numbers. > This is the new website of the project http://ltworf.github.io/weborf/ > > It comes with a GUI for easy directory sharing, that opens external ports > from inside NAT. > > The server supports being started by xinetd, supports CGI, partial download, > and webdav, so you can use it to mount directories with davfs remotely. > > When doing so has a (so far unique) cache for dynamic content that greatly > reduces the CPU load, because it avoids re-creating all the XML over and > over (clients tend to send the same request tens of times). > > It can also be used to send over a whole directory as .tar file, when > started with the appropriate parameter. > > Best. Ok, I'll leave this open then =) |