openupload-devel

[openupload-devel] 2 ideas for OpenUpload

[Andy H. <and...@eu...>]

I have two ideas that I would like the community's input on.  These 
ideas are coming from a corporate/enterprise type scenario and may not 
be applicable to everyone.  The first one is pretty straight forward and 
should be fairly simple for a developer.  The second one is a little 
more complex.

1.  I would like to be able to scan files for viruses after upload.  
Normally, you would scan the stream during upload, but I don't object to 
writing the file to disk and then scanning it.  I am using the site on a 
linux server and I am looking at php-clamavlib.  I am sure that we would 
want this to be a plugin form.  I might be able to hack through this 
with some help.

http://www.howtoforge.com/scan_viruses_with_php_clamavlib

2.  The second item is related to the way the system works.  OpenUpload 
is great for our organization for transferring file from inside the 
company to vendors, customers, etc.  For transferring large files from 
customers, vendors, etc inbound to our internal users, not so much.

I realize that the ultimate correct solution would be for the vendors, 
customers, etc to get their own OpenUpload server and provide us a place 
to download their files.  However, the sad truth is that many 
organizations are not going to do this and I will still have users that 
need to get the files from outside.

If I were going to design a tool that works for outside in transfers, I 
think it should work like this:

1. Internal user with an account logs in to the OpenUpload site.
2. Internal user fills out form very similar to existing form and sends 
it to vendor, customer, whoever
3. External user receives email with one time random alphanumericly 
generated url and included password from internal user.
4. External user clicks link and goes to OpenUpload site and is allowed 
to upload file(s).
5. Internal user receives email with link to download file and password.

It seems like all of the peices are there, they just need to be 
re-arranged.  I would be interested to know what others think about this 
both the need and the solution.  I think it would make a great addition 
as an additional mode that the site can operate in.  Perhaps it would 
require a separate site to live in, but I'm not sure that would be such 
a bad thing.

Like:
inbound.transfers.com
outbound.trnasfer.com
each operating in a different mode.

-Andy

Re: [openupload-devel] 2 ideas for OpenUpload

[Alessandro B. <ts...@br...>]

Andy, both of this requests are in the "Feature Requests".

Andy Hester ha scritto:
> I have two ideas that I would like the community's input on.  These 
> ideas are coming from a corporate/enterprise type scenario and may not 
> be applicable to everyone.  The first one is pretty straight forward and 
> should be fairly simple for a developer.  The second one is a little 
> more complex.
> 
> 1.  I would like to be able to scan files for viruses after upload.  
> Normally, you would scan the stream during upload, but I don't object to 
> writing the file to disk and then scanning it.  I am using the site on a 
> linux server and I am looking at php-clamavlib.  I am sure that we would 
> want this to be a plugin form.  I might be able to hack through this 
> with some help.
> 
> http://www.howtoforge.com/scan_viruses_with_php_clamavlib
> 

The antivirus is pretty straight forward (very similar to the compress 
plugin, imho). And am not really sure it needs to use that lib

I'm neutral (+0) on this one.

> 2.  The second item is related to the way the system works.  OpenUpload 
> is great for our organization for transferring file from inside the 
> company to vendors, customers, etc.  For transferring large files from 
> customers, vendors, etc inbound to our internal users, not so much.
> 
> I realize that the ultimate correct solution would be for the vendors, 
> customers, etc to get their own OpenUpload server and provide us a place 
> to download their files.  However, the sad truth is that many 
> organizations are not going to do this and I will still have users that 
> need to get the files from outside.
> 
> If I were going to design a tool that works for outside in transfers, I 
> think it should work like this:
> 
> 1. Internal user with an account logs in to the OpenUpload site.
> 2. Internal user fills out form very similar to existing form and sends 
> it to vendor, customer, whoever
> 3. External user receives email with one time random alphanumericly 
> generated url and included password from internal user.
> 4. External user clicks link and goes to OpenUpload site and is allowed 
> to upload file(s).
> 5. Internal user receives email with link to download file and password.
> 
> It seems like all of the peices are there, they just need to be 
> re-arranged.  I would be interested to know what others think about this 
> both the need and the solution.  I think it would make a great addition 
> as an additional mode that the site can operate in.  Perhaps it would 
> require a separate site to live in, but I'm not sure that would be such 
> a bad thing.
> 
> Like:
> inbound.transfers.com
> outbound.trnasfer.com
> each operating in a different mode.
> 

This would need some coding and a new db table for the tokens, but it's 
defenately a must have option.

+1 on this one.

Don't think that the different "domains" is needed, but it could be an 
option (you'd probably need to maintain the 2 different sites though, or 
use the modrewrite ...)


I plan on implementing this in next version (0.5 which I plan should 
have some major structure changes, but minimal to the user/admin), but 
if you provide patches I'll be pleases to push them (we can still do a 
0.4.1 version :) )

Alessandro

Re: [openupload-devel] 2 ideas for OpenUpload

[Peter V. <pv...@dy...>]

am 06.05.2009 18:16 schrieb Andy Hester:
> 2.  The second item is related to the way the system works.  OpenUpload 
> is great for our organization for transferring file from inside the 
> company to vendors, customers, etc.  For transferring large files from 
> customers, vendors, etc inbound to our internal users, not so much.

Yeah! We managed to bring biggies of up to 700MB by means of OpenUpload
to the outside world. I promised to my users: "I will look for a
solution where customers can send big files in."

So, I would really like to have such a feature implemented in OpenUpload!

> 1. Internal user with an account logs in to the OpenUpload site.
> 2. Internal user fills out form very similar to existing form and sends 
> it to vendor, customer, whoever
> 3. External user receives email with one time random alphanumericly 
> generated url and included password from internal user.
> 4. External user clicks link and goes to OpenUpload site and is allowed 
> to upload file(s).
> 5. Internal user receives email with link to download file and password.

The handling for the customer has to be as simple as possible and the
above proposal sounds quite simple.

Peter