Having problems with message search?
However, it's probably best to ditch the extra MANIFEST.MF and/or WEB-INF data. Those are Java-specific forms of Meta Data. I was thinking of a similar idea, but in JSON format:
The nice thing about using JSON is that it leaves the option open for client-based integration. e.g. Rather than having a JSP or PHP page write out an IFRAME or include the script, I could have a bit of AJAX code read the extracted manifest from the server and generate the correct elements to display the application.
Thanks!
Jerason
On Tue, Jan 6, 2009 at 11:49 AM, Leonardo <sombriks@...> wrote:
starting to understand....
since the real entry point for the javascript app remains some document, that document could have standart default information block, but it does not solve the problem about package all files on a easy way.
i've suggested .war because it's just a .zip file, the java-ish info (located inside *-INF folders) can easily be ignored.2009/1/6 Jerason Banes <jbanes@...>
As in Java Web Application Archives? Doesn't that seem a bit heavy-weight? WAR files would have to be deployed as complete Java applications on a servlet-capable server. My concern is that this would destroy server portability, and I don't think it's a safe bet that most hosting services would be running a Java-based server.
(...)
Offline 
Send Email