We are working on a module that allows specific file types to be
uploaded. These files since are uploaded to and remain in Active4D's web
root /web/upload/.. . In our case Active4D sits behind a standard web
server (WebSTAR now, Apache very soon) and all requests pass through
rewrite rules.
The uploaded files are types that wouldn't normally be served by
Active4D. Our rewrite rules are defined so that requests for these file
types would normally be handled by the web server (.txt, .doc, .xls,
.pdf, .gif, .jpg. .tif)
Once a file is uploaded other users may need to access these files
through their browser.
I'm trying to figure out the best way to handle this? Here are some ideas:
1) Have a process watch the upload folder for new files and move them
into into WebSTAR (or Apache's) web root? Having not done that am I
going to run into permissions problems?
2) Same strategy as 1 but move them into an FTP-accessible folder? Or
make web/upload accessible via anonymous FTP?
3) Write an Active4D method that given a parameter that identifies the
file, reads the file and serves it? In our case we've set a 2MB file
size limit.
Can others comment on these, or other strategies?
Thanks,
Brad Perkins
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
