LiveCode Forums.

I've been looking at LiveCode Hosting. From their FAQ:

The new server engine (due in July) will support "running stacks on the server". What does this mean?

The feature allows the revserver engine to load stacks, and run code from there - in the same way that the legacy 'CGI' engine does now. Please note that this does not mean that a stack running on the server presents itself to the web-browser.

Does that mean that my stacks will run without the user having to download the web plugin?

No, there are different concepts involved here. Deployment to the web via creating a standalone that is published to a web page and then runs in a browser which has the web plugin installed is a client-side scenario. The stacks are delivered to the browser and run in the context of the client's local machine. Your obvious comparison here is with Flash.
Deployment via on-rev or reserved is a server side environment that is more akin to php. You can create scripts in livecode that can be used to create dynamic web pages and services, like you can with php. The scripts can be wholly livecode or have online code interspersed with html in the same way that you can with (yes, I'm going to mention it again) php. These run in the server side context and output content that can be viewed by the client's browser, etc, but the processing is all done server side. To date, it has only been possible to run a livecode script via on-rev or reserved as a text file. To be able to have a library of handlers and modules in a stack that means you can use custom properties, stack-specific hierarchy and handlers, and (probably most important to many potential users) use existing stack libraries like libUrl and encrypt/protect the code is very desirable.
The announcement means that this feature, to be able to load a stack in the server side context, rather than just a text file script, is going to be available soon. It is not connected to any developments concerning the web plugin save that the development of any part of livecode is intrinsic to the rest of it.

Thanks for taking the time to explaining this--

To be able to have a library of handlers and modules in a stack that means you can use custom properties, stack-specific hierarchy and handlers, and (probably most important to many potential users, the use existing stack libraries like libUrl, and to be able to encrypt & protect the code is very desirable.

I see they've just added MySQL and Postgres database support.
And PHP Bulletin Board support. (That's what runs this forum.)
I'm particularly interested in the LiveCode Desktop Site Management platform.