Livecode Server 4.6.3 - First impressions pt2 - using the new version at Dreamhost

Andre Garzia andre at andregarzia.com
Wed Jul 27 20:03:47 EDT 2011


Stephen,

be aware that loading large stacks into memory will get you to the memory
protection police! If your database stack is too big, and lots of copies are
loaded for all the requests, Apache or whoever does the purging might kill
your engine to save resources. This is hardcoded into On-Rev accounts. The
engine on dreamhost should not have these limits but still, dreamhost is a
shared server and they will probably kill processess that starte the server
of its resources.

Cheers
andre

On Wed, Jul 27, 2011 at 7:38 PM, stephen barncard <
stephenREVOLUTION2 at barncard.com> wrote:

> *LIVECODE SERVER 4.6.3*
>
> Wow. Haven't done any speed benchmarks, and I've just started using this
> version of LCS, but it offers what was missing before, and a lot more.
>
> Stacks are full fledged citizens now .  One can 'start using stack x' -
> one's  tested land-based libraries can be used at sea.
>
> This is a ****** big deal!
>
> One can create, delete and open stacks
>
> stacks mean
>
> One can set and get custom properties of any dimension
> One can add and delete cards for more dimensions
> One can store and obfuscate binary files in props
> many dimensions  /stack/card/propertyset/property/property/property ... etc
>
> caveats:
>
> no objects are allowed 'on' stacks. This will crash your code. (expected)
> stacks must be saved immediately after changes, before the handler quits.
>
> uses:
>
> sitewide database tasks - saving visitor data in an array
> libraries can be thoroughly debugged on the desktop and run intact in the
> server environment
>
>
>
> And here's my little editing surprise.
>
> I had the IDE open for the dictionary, and had accidentally clicked on the
> test *testprops.rev* file in the list in Transmit (the excellent FTP client
> from Panic Software).  I expected to see the jumble of binary that usually
> shows in text editors. Instead, it loaded into the open Livecode IDE!
>
> I looked at the stack - it had all the changes I did and saved online. Then
> I made some updates in the stack in the IDE, and saved it back to the site,
> and they stuck!
>
> I don't remember everything working like this before.
>
> Round trip - edit compile save run  - the ultimate speed design setup.
> Stacks are now on a par with text files for online editing ease.
>
> Another thing - the "inline" error messages are much better than before -
> more informative and right on the money.
>
>  Great work REv team.
>
>
>
> --
>
>
>
> Stephen Barncard
> San Francisco Ca. USA
>
> more about sqb  <http://www.google.com/profiles/sbarncar>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
http://www.andregarzia.com All We Do Is Code.



More information about the use-livecode mailing list