|
Adding to what Tim said about single page apps. The entry point of the
application might be a very small static HTML skeleton. Add to that page a
reference to a JavaScript framework that transforms it into something
meaningful by having the browser merge skeleton HTML with JSON at runtime,
which might be requested asynchronously from the server. For example:
http://rd.radile.com/rdweb/phones/phonelist.html#phones
The page alternates between list and detail content by clicking a hyperlink
or the browser back button.
You don't need PHP or any other web-service layer to get an app like that
working. The page might simply reference static JSON or XML, comparable to
the sample shared in the original post.
After you get the app doing what you want, you can change references from
static JSON or XML, to a request that interfaces with a web service (and a
database).
By the way, Tim. How do you use single page apps in business contexts?
Nathan.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.