in reply to Re: Cgi params as binary data
in thread Cgi params as binary data

Okay, the problem is, I don't actually have a param('uploaded_file'). There's no file-NAME associated with the binary data I want to output.

Once I process the uploaded zipfile, the processed output is raw binary data that gets generated (What's really going on, is that I feed the uploaded file to an external java program, then that java program spits out raw binary data, that raw binary data is a zip file)

Maybe I can do something like upload($binary_contents) or something like that?

Regarding the DOS service attacks, it's a script that would be used by only a handful of people internally, so that's not really something I'm concerned about. We should be okay with a slow running, memory hogging script. :-)

Replies are listed 'Best First'.
Re^3: Cgi params as binary data
by davido (Cardinal) on Jun 05, 2011 at 02:49 UTC

    With all the support out there for storing session data (including larger files), why the strong aversion to doing it the traditional way? If you need to maintain data across page loads, you're maintaining a session's state. CGI::Session helps with that. And it's just one of many. Also Apache::Session, and many others. Dealing with session data becomes simple if you use the right tool.


    Dave

      ooo! This might be exactly what I need....