Thursday, July 12th, 2007
The new release is huge, literally, since it has gone from < 150 KB back in 2005, to 5.3 MB today. This is mostly due to the new server side code based on Helma.
On the client side, there is now Google Gears support:
- If your end-user has Google Gears installed, they can execute the web-app primarily within the web-browser. Here, the client-side RDBMS is an asynchronously replicated cache of records from the main server-side RDBMS. The big benefit is increased UI responsiveness. And, the web-app can go offline and survive down or flaky network connections. By flaky, Iâ€™m thinking iPhone on AT&T, or 200 attendees trying to share a conference WiFi hotspot.
- If your end-user does not have Google Gears, no problem. They can still execute the web-app completely within the web-browser, for increased UI responsiveness. And, the web-app can still survive flaky network connections. Here, the client-side RDBMS is not persistent, just a memory-only SQL engine. The downside with a memory-only DB is you canâ€™t truly go offline where you power-cycle, or close and restart your web-browser.
- The last option is where your application code executes on the server side, running on a traditional-style, server-side web application server. It communicates directly with the full, main RDBMS that is the source of truth. While not as snappy as the browser-hosted web-app, at least the user is working with the full set of data, not a cached subset, minimizing outdated views of information. Also, the pages served up by the web application server are crawlable, if you wish, by your favorite search engines.
I met Steve Yen a long time ago and we chatted about Junction as well as other topics. He is a very smart guy, and it is great to see him back in the TrimPath game….. at the perfect time.
Posted by Dion Almaer at 7:07 pm