Re: Web App Resource/Asset Bundler ?

[perrin]

Usually people use a tarball for this, with the perl code and other stuff in it. What problem are you trying to solve by putting the data into your module instead?

[renodino]

I'm trying to simplify deployment for standalone web apps, ie, browser based GUI apps. Instead of running under Apache or somesuch, a web app would include its own web server module (eg, HTTP::Server::Simple, HTTP::Daemon, HTTP::Daemon::Threaded, etc.). Assuming the app might eventually be packaged into an exe (via PAR, perl2exe, etc.), or even installed as a std. Perl package, it would be nice to have all the assets handled in the "Perlish" way, wo/ the hassle of trying to figure out the directory structure where the assets reside.

So if the assets are all rolled into Perl modules, the app can just introspect to get datetime info, and roll HTTP headers as appropriate, doing any decoding/decompressing as needed.

[perrin]

I think it would be a lot easier to package the whole thing as a tarball or other installer package and use relative paths in your scripts.