How do you do Ajax when there's no server?
In corporate America, you can't just put up a webserver whenever and wherever you want. There's no webserver on our NT network folders, but there's a lot of documents and metadata there. There's no webserver connected to the source code and data in our version management application -- there's a Windows GUI and DOS commands, but there ain't no webserver. We've got the same problem with our Lotus Notes databases, UniVerse and Oracle databases, and emails and calendars in Outlook. There's not even a webserver running on my own darn workstation, because I don't have administrative access to it.
You can't have an asynchronous conversation if there's no one listening. So you gotta be creative. You could copy the data to some place where there is a webserver. You could generate files that can be read by web pages.
Generating Files
You could generate HTML files. You would have to combine the content and style together, and your web application would either include the generated HTML in a frameset or an iframe, or transfer control altogether.
You could generate XML files. You could use XML data islands, but I think you need a server for that. Maybe you could transform it into HTML with XSLT and the result could be styled with CSS.
You could generate JSON files. Hmmm, that's interesting... You could either load them up with a script tag, or generate a script element dynamically.
Thursday, January 11, 2007
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment