pink wrote:
> I've used "LSON" in the past and had issues. Not with save files, but
> with socket transmission...
>
> I may play around a bit and see how things go
LSON is binary, so set headers accordingly. When in doubt, base64.
I have two systems that use LSON almost exclusively to move data
ble.com/CouchDB-DayBed-etc-tp4718761p4718956.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscripti
pink wrote:
> Daybed's built in local storage system is the save stack, works well
> on all platforms.
Have you considered LSON files (LiveCode encoded arrays)?
Where I used to use stack files for some storage options, I've been
migrating to LSON with two benefits:
- Being raw data outside o
Alex
> On 23 Aug 2017, at 22:28, Alex Tweedly via use-livecode
> wrote:
>
> With the exception of a couple of things that basically scraped data off some
> web pages, every app I've done in the last couple of years (all for personal
> use by myself or friends - I'm a hobbyist) have shared on
ication, a lesson on creating a production ready server with SSL, and I
am planning on a section about setting up a cluster.
-
---
Greg (pink) Miller
mad, pink and dangerous to code
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/CouchDB-DayBed-etc-tp4718761p47
Alex,
> local storage, and that data is subsequently
> synched to "the cloud”
You might want to take a look at Mark Talluto’s LiveCloud.
http://livecloud.io
And I agree Greg's Daybed library and CouchDB course are very good.
Jim Lambert
___
use-live
Just a quick thank you to Greg for the info on his Daybed library, and
for the Udemy course on CouchDB. I found the course fascinating - and I
watched it first so I had the overview before watching the Daybed
specific talk in Livecode Global.
(And I have to admit I watched it all on 1.5x speed