Re: Lifecycle - booting up web apps

On Tuesday, September 6, 2011 at 8:05 PM, Kevin Peno wrote:

> >  The cons is that I need to hack bootstrap.js. The use case I wanted to focus on was starting an application from the command line (as I assume the App is a black box … like a zip file).
>  
>  I'm not sure what you'd have to hack about it. Most languages provide a way to get command arguments. For example: PHP's $argv, Java/C# main( args[] ). In all cases it would be up to the application to handle processing those arguments and user-agent to support that language. Support including how to pass it start up args (whether they be from query string, etc) and, possibly, calling start up methods. The PI could be expanded to specify the argument handling method used by the implementer (ex.. method="args" or method="POST"), or maybe it just becomes part of the markup.  
Ok, so I'm again thinking of w3c widgets (or a packaged application). To change bootstrap.js, I need to unzip the file, change the bootstrap.js, then rezip it, then launch it. What I really want is just to run it from the command line and not change anything:

../fooapp --do this  

> As far as "black box" goes. I don't see how that matters much in regards to this spec.  

If you mean that bootstrap.js would be the "handler" for command line arguments, then yes.  

> This would be up to the implementor to handle. For example, PHP has a jar-like system called phar. When a phar is loaded, you can include other files from within the phar, but the phar format and processor handles how to find those files. It also handles mapping the relationships of whatever I pass into phar upon "compile". I assume jar works very similar, but I have limited experience with Java. If I'm missing something I apologize!  
I think we are just brainstorming :)

Received on Thursday, 8 September 2011 12:02:52 UTC