Forgive my seeming obsessiveness over this thread, but having ported
some rather non-trivial projects to the web over the last few years it's
a topic of especially keen interest to me, always eager to find a
panacea only to find El Dorado instead.
I've been running Rev-based CGIs well for
This issue came to light in a thread I came across in the RB forums, eager
as I am to learn more about their implementation.
This thread notes how Dreamhost -- where I run a great many Rev CGIs,
including the blog at LiveCodeJournal.com -- recently nixed an RB app
because it was attempting
And we now have $_SESSION in Livecode Server 5.0 ! Yes!
On 23 September 2011 12:34, Andre Garzia an...@andregarzia.com wrote:
This issue came to light in a thread I came across in the RB forums,
eager one of the ways that PHP $_SESSION works, it is simple to implement
and the
data is not
Richard,
Le 23 sept. 2011 à 21:19, Richard Gaskin a écrit :
A way to avoid this is to have the app always running, as a sort of daemon
process, listening on a specified socket for incoming instructions.
The problem with that is that it'll only be allowed on dedicated servers or
some
After all the work they have already done on IE 12.5??
Bob
On Sep 23, 2011, at 12:19 PM, Richard Gaskin wrote:
(how nice the world would be if IE would simply die the death it deserves
after so many years of thumbing its nose at well-published standards).
Richard,
Actually, I think a decent first step is to just create apps which run on a
single page. This removes much if not all the necessary session information
and works pretty much like typical AJAX apps do now.
Of course, later having the app being able to communicate with LC Server
might be
I don't use !important but use a lot of inline css for special cases and use
css as a sheet or in the header for more general specs (for a one-pager).
I pass the state of the app through POST or GET which gets trapped at the
beginning and decides which 'page' to display.
With the new two pass
