Re: LiveCode and Websockets
Charles, A WebSockets external would be very beneficial for everyone doing web stuff from LC. I am looking forward to checking it out when it is released. :-) Thanks a lot for working on this. Cheers andre On 11/26/2018 6:24 AM, Charles Warwick via use-livecode wrote: Hi Bob, The external is still in development, so I have not yet uploaded any information or documentation to the web. I am happy to send you the latest beta version along with a few sample scripts if you are interested, just send me an e-mail directly. Regards, Charles On 25 Nov 2018, at 12:44 am, "b...@bobhall.net" wrote: Charles, I would like to find out more about your socket external specifically for websockets. Can you point me to where I can find out about the socket external? Thanks, Bob Hall On Nov 23, 2018, at 1:10 AM, Charles Warwick via use-livecode wrote: Hi Todd, Depending on what platforms you need to support, I have a socket external for LiveCode that includes the ability to use websockets. Cheers, Charles ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and Websockets
Hi Bob, The external is still in development, so I have not yet uploaded any information or documentation to the web. I am happy to send you the latest beta version along with a few sample scripts if you are interested, just send me an e-mail directly. Regards, Charles > On 25 Nov 2018, at 12:44 am, "b...@bobhall.net" wrote: > > Charles, > > I would like to find out more about your socket external specifically for > websockets. Can you point me to where I can find out about the socket > external? > > Thanks, > Bob Hall > >> On Nov 23, 2018, at 1:10 AM, Charles Warwick via use-livecode >> wrote: >> >> Hi Todd, >> >> Depending on what platforms you need to support, I have a socket external >> for LiveCode that includes the ability to use websockets. >> >> Cheers, >> >> Charles > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and Websockets
Thanks Charles for the reply. Hope all is going well with you. Where can I test the WebSocket external? I will need it for iOS, Android, Mac, and Windows. Can you email me directly as we are time sensitive on this please. We have the server up and running. Socket.io is the BEST in the market and can deal with 10,000+ simultaneous connections with Node.js as the server. Also, thanks, Tom. I looked at this and what it does is create a bridge between LC and a web browser JavaScript that you add to the form. This is a GREAT workaround if we can find our own controller. I see they need some more Javascript code to manage all the different callback and error trapping functionality, but it is a workable solution we also had considered. It is NOT as flexible as an external, but we will improve it to make it work to keep it as a backup. Thanks guys, Todd Fabacher ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and Websockets
Charles, I would like to find out more about your socket external specifically for websockets. Can you point me to where I can find out about the socket external? Thanks, Bob Hall > On Nov 23, 2018, at 1:10 AM, Charles Warwick via use-livecode > wrote: > > Hi Todd, > > Depending on what platforms you need to support, I have a socket external for > LiveCode that includes the ability to use websockets. > > Cheers, > > Charles ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and Websockets
ps > requires websocketd to go along with it. On Fri, Nov 23, 2018 at 1:46 AM Tom Glod wrote: > Todd, this was posted here a little while ago..haven't tested it, but > apparently its websockets for livecode. Let us know how it goes. > > https://github.com/samansjukur/wslc > > On Fri, Nov 23, 2018 at 1:10 AM Charles Warwick via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> Hi Todd, >> >> Depending on what platforms you need to support, I have a socket external >> for LiveCode that includes the ability to use websockets. >> >> Cheers, >> >> Charles >> >> > On 23 Nov 2018, at 4:09 pm, Todd Fabacher via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> > >> > We have hot a wall because we have an API that is ONLY accessible via a >> > call to Socket.io server using Websockets. >> > >> > Richard Gaskin, I remember you were looking into this last year, any >> > success from your research. >> > >> > It seems the best way would be to open a web browser and code the >> > communications using Javascript, which would then all a LiveCode >> function >> > on the callback. >> > >> > Any suggestions would be appreciated!! >> > >> > Much Thanks, >> > >> > --Todd >> > ___ >> > use-livecode mailing list >> > use-livecode@lists.runrev.com >> > Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> > http://lists.runrev.com/mailman/listinfo/use-livecode >> > >> >> >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and Websockets
Todd, this was posted here a little while ago..haven't tested it, but apparently its websockets for livecode. Let us know how it goes. https://github.com/samansjukur/wslc On Fri, Nov 23, 2018 at 1:10 AM Charles Warwick via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Todd, > > Depending on what platforms you need to support, I have a socket external > for LiveCode that includes the ability to use websockets. > > Cheers, > > Charles > > > On 23 Nov 2018, at 4:09 pm, Todd Fabacher via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > We have hot a wall because we have an API that is ONLY accessible via a > > call to Socket.io server using Websockets. > > > > Richard Gaskin, I remember you were looking into this last year, any > > success from your research. > > > > It seems the best way would be to open a web browser and code the > > communications using Javascript, which would then all a LiveCode function > > on the callback. > > > > Any suggestions would be appreciated!! > > > > Much Thanks, > > > > --Todd > > ___ > > use-livecode mailing list > > use-livecode@lists.runrev.com > > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > > http://lists.runrev.com/mailman/listinfo/use-livecode > > > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and Websockets
Hi Todd, Depending on what platforms you need to support, I have a socket external for LiveCode that includes the ability to use websockets. Cheers, Charles > On 23 Nov 2018, at 4:09 pm, Todd Fabacher via use-livecode > wrote: > > We have hot a wall because we have an API that is ONLY accessible via a > call to Socket.io server using Websockets. > > Richard Gaskin, I remember you were looking into this last year, any > success from your research. > > It seems the best way would be to open a web browser and code the > communications using Javascript, which would then all a LiveCode function > on the callback. > > Any suggestions would be appreciated!! > > Much Thanks, > > --Todd > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
LiveCode and Websockets
We have hot a wall because we have an API that is ONLY accessible via a call to Socket.io server using Websockets. Richard Gaskin, I remember you were looking into this last year, any success from your research. It seems the best way would be to open a web browser and code the communications using Javascript, which would then all a LiveCode function on the callback. Any suggestions would be appreciated!! Much Thanks, --Todd ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and WebSockets
Many thanks for this useful reference link Andrew Le 9 juil. 2013 à 02:32, Andrew Kluthe a écrit : > I had read that, and found some other useful info here as well. > https://github.com/LearnBoost/socket.io-spec > > Andrew -- Pierre Sahores mobile : 06 03 95 77 70 www.sahores-conseil.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and WebSockets
>> Would you care to discuss the difference between websockets and the >>socketswe work with in livecode or point me to some basic information on the websocket implementation you think we could implement in pure livecode? What things would keep it from working very efficiently? I see you already have some good references. Proper websockets implement a protocol on top of standard TCP socket connections on port 80. I think you could write or port an implementation of this protocol directly using the sockets available in desktop LiveCode. For socket.io there are also other transports available (i.e. web sockets are emulated over some other transport). I think it might be possible to implement the XHR-polling transport in LiveCode, using load URL for the GET request (with the header set to keep the connection alive - it doesn't return anything until the server wants to send you something) and doing standard HTTP posts. What I don't know is whether LiveCode can actually do a POST request while you still have an async load operation running, or whether it will keep the HTTP connection alive as required by XHR-polling (a.k.a. long polling) rather than just timing out?? As for efficiency, LiveCode has pretty good performance because the language is very high level, so each line of code typically does quite a lot in native code in the engine underneath. Implementing a protocol is quite a low-level thing to do in such a high-level language, parsing/formatting all the messages in LiveCode directly is probably quite computationally expensive vs just putting/getting the content of those messages into/from a "websocket object" that handles the formatting/parsing for you in native code. Also, as Pierre said, you could kludge this through the browser too, using the socket.io client directly. That's going to be much, much less efficient though. Mark ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and WebSockets
Thanks Pierre, I'm pretty sure I could make something like that work but it's a nasty kludge, I'm not in any hurry (busy with non-LiveCode projects at the moment anyway) and when I get around to looking at it, I want to do it properly. :) From: Pierre Sahores To: How to use LiveCode Sent: Tuesday, 9 July 2013, 0:56 Subject: Re: LiveCode and WebSockets Mark , Should work (untested) : Node.js on the server side + revBrowser (desktop) or mobileBrowser (iOS/android) + some js + client-side pseudo urls to get catched by : on browserLoadRequested pUrl, pType -- prefered on the iOS platform (desktop platforms untested) end browserLoadRequested and on browserStartedLoading pUrl -- prefered on the Android platform (desktop platforms untested) end browserStartedLoading to being able to exchange bidirectional messages between your web layer to the native livecode one. note : your web view pseudo URLs needs to match existing files (workingpath/file.html…) in your client app sandboxed cache or document directory to be catchable on the Android platform at least. To maintain a common codebase with the iOS app, i have the habit to create the on this platform too. Pierre ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and WebSockets
Thanks Phil, I had read that, and found some other useful info here as well. https://github.com/LearnBoost/socket.io-spec Andrew On Mon, Jul 8, 2013 at 6:56 PM, Pierre Sahores wrote: > Mark , > > Should work (untested) : > > Node.js on the server side + revBrowser (desktop) or mobileBrowser > (iOS/android) + some js + client-side pseudo urls to get > catched by : > > on browserLoadRequested pUrl, pType > -- prefered on the iOS platform (desktop platforms untested) > end browserLoadRequested > > and > > on browserStartedLoading pUrl > -- prefered on the Android platform (desktop platforms untested) > end browserStartedLoading > > to being able to exchange bidirectional messages between your web layer to > the native livecode one. > > note : your web view pseudo URLs needs to match existing files > (workingpath/file.html…) in your client app sandboxed cache or document > directory to be catchable on the Android platform at least. To maintain a > common codebase with the iOS app, i have the habit to create the on this > platform too. > > Pierre > > Le 8 juil. 2013 à 20:35, Mark Wilcox a écrit : > > > We know, I'm interested in websockets for realtime comms between apps. > Right now I think it'd be possible to implement one or more of the > supported transports for socket.io in pure LiveCode but maybe not very > efficiently. An alternative would be to wrap existing native > implementations as externals. I've not looked into it in any great depth as > I'm basically waiting for the engine refactoring to be completed before > trying to hook new stuff in. > > > > Pierre Sahores wrote: > > > >> The HTTP(S) REST architecture is full supported on any LC desktop or > mobile platform, iOS and Android included. They can be set to act as > clients of any kind of nTier server side application (LC-Server, PHP, RoR, > etc...). > >> > >> Le 8 juil. 2013 à 18:19, Mark Wilcox a écrit : > >> > >>> I'm interested in using something like socket.io as part of a backend > for mobile (and maybe also desktop) apps. However, we don't have proper > sockets support on mobile (without externals at least) and websockets are > very definitely not the same thing as standard sockets. > >>> > >>> What do you have in mind? I'm certainly interested in discussing it. > >>> > >>> Mark > >>> > >>> > >>> > >>> From: Andrew Kluthe > >>> To: How to use LiveCode > >>> Sent: Monday, 8 July 2013, 16:05 > >>> Subject: LiveCode and WebSockets > >>> > >>> > >>> I have been learning a little bit about websockets lately for a > project and > >>> I have never really played around with livecode's socket communication > >>> methods. This makes me curious. > >>> > >>> Is there anyone else on the list that might be more familiar with both > that > >>> would be interested in discussing using something like socket.io as > part of > >>> a backend for livecode desktop applications? > >>> > >>> > >>> -- > >>> Regards, > >>> > >>> Andrew Kluthe > >>> and...@ctech.me > >>> ___ > >>> use-livecode mailing list > >>> use-livecode@lists.runrev.com > >>> Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > >>> http://lists.runrev.com/mailman/listinfo/use-livecode > >>> ___ > >>> use-livecode mailing list > >>> use-livecode@lists.runrev.com > >>> Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > >>> http://lists.runrev.com/mailman/listinfo/use-livecode > >> > >> -- > >> Pierre Sahores > >> mobile : 06 03 95 77 70 > >> www.sahores-conseil.com > >> > >> > >> ___ > >> use-livecode mailing list > >> use-livecode@lists.runrev.com > >> Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > >> http://lists.runrev.com/mailman/listinfo/use-livecode > > ___ > > use-livecode mailing list > > use-livecode@lists.runrev.com > > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > > http://lists.runrev.com/mailman/listinfo/use-livecode > > -- > Pierre Sahores > mobile : 06 03 95 77 70 > www.sahores-conseil.com > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- Regards, Andrew Kluthe and...@ctech.me ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and WebSockets
Mark , Should work (untested) : Node.js on the server side + revBrowser (desktop) or mobileBrowser (iOS/android) + some js + client-side pseudo urls to get catched by : on browserLoadRequested pUrl, pType -- prefered on the iOS platform (desktop platforms untested) end browserLoadRequested and on browserStartedLoading pUrl -- prefered on the Android platform (desktop platforms untested) end browserStartedLoading to being able to exchange bidirectional messages between your web layer to the native livecode one. note : your web view pseudo URLs needs to match existing files (workingpath/file.html…) in your client app sandboxed cache or document directory to be catchable on the Android platform at least. To maintain a common codebase with the iOS app, i have the habit to create the on this platform too. Pierre Le 8 juil. 2013 à 20:35, Mark Wilcox a écrit : > We know, I'm interested in websockets for realtime comms between apps. Right > now I think it'd be possible to implement one or more of the supported > transports for socket.io in pure LiveCode but maybe not very efficiently. An > alternative would be to wrap existing native implementations as externals. > I've not looked into it in any great depth as I'm basically waiting for the > engine refactoring to be completed before trying to hook new stuff in. > > Pierre Sahores wrote: > >> The HTTP(S) REST architecture is full supported on any LC desktop or mobile >> platform, iOS and Android included. They can be set to act as clients of any >> kind of nTier server side application (LC-Server, PHP, RoR, etc...). >> >> Le 8 juil. 2013 à 18:19, Mark Wilcox a écrit : >> >>> I'm interested in using something like socket.io as part of a backend for >>> mobile (and maybe also desktop) apps. However, we don't have proper >>> sockets support on mobile (without externals at least) and websockets are >>> very definitely not the same thing as standard sockets. >>> >>> What do you have in mind? I'm certainly interested in discussing it. >>> >>> Mark >>> >>> >>> >>> From: Andrew Kluthe >>> To: How to use LiveCode >>> Sent: Monday, 8 July 2013, 16:05 >>> Subject: LiveCode and WebSockets >>> >>> >>> I have been learning a little bit about websockets lately for a project and >>> I have never really played around with livecode's socket communication >>> methods. This makes me curious. >>> >>> Is there anyone else on the list that might be more familiar with both that >>> would be interested in discussing using something like socket.io as part of >>> a backend for livecode desktop applications? >>> >>> >>> -- >>> Regards, >>> >>> Andrew Kluthe >>> and...@ctech.me >>> ___ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >>> ___ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> >> -- >> Pierre Sahores >> mobile : 06 03 95 77 70 >> www.sahores-conseil.com >> >> >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode -- Pierre Sahores mobile : 06 03 95 77 70 www.sahores-conseil.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and WebSockets
On 7/8/13 11:51 AM, Andrew Kluthe wrote: However, we don't have proper sockets support on mobile (without externals at least) I am mainly interested in desktop apps at the moment simply because we are doing most of our mobile apps as mobile web apps. However, this will change likely in the next few years if we were to see sockets and UI (resolution independence, etc) improvements on mobile. and websockets are very definitely not the same thing as standard sockets. I am having a hard time just finding straight forward info on the lower level websocket information. As of right now all the information I am finding is how to use websockets within this framework or that framework and nothing really about the differences between websockets and standard sockets. Hi Andrew, Maybe this will help some: http://en.wikipedia.org/wiki/WebSocket Phil Davis Also, socket programming in general (and in livecode) is new to me because up until now I have wrote most of my applications using http interfaces. Not having a non-blocking http client is really getting in the way of some of the things I want to do with livecode and I really would like realtime notifications, broadcasting, etc. Would you care to discuss the difference between websockets and the sockets we work with in livecode or point me to some basic information on the websocket implementation you think we could implement in pure livecode? What things would keep it from working very efficiently? Thanks for taking the time to respond, Andrew On Mon, Jul 8, 2013 at 1:35 PM, Mark Wilcox wrote: We know, I'm interested in websockets for realtime comms between apps. Right now I think it'd be possible to implement one or more of the supported transports for socket.io in pure LiveCode but maybe not very efficiently. An alternative would be to wrap existing native implementations as externals. I've not looked into it in any great depth as I'm basically waiting for the engine refactoring to be completed before trying to hook new stuff in. Pierre Sahores wrote: The HTTP(S) REST architecture is full supported on any LC desktop or mobile platform, iOS and Android included. They can be set to act as clients of any kind of nTier server side application (LC-Server, PHP, RoR, etc...). Le 8 juil. 2013 à 18:19, Mark Wilcox a écrit : I'm interested in using something like socket.io as part of a backend for mobile (and maybe also desktop) apps. However, we don't have proper sockets support on mobile (without externals at least) and websockets are very definitely not the same thing as standard sockets. What do you have in mind? I'm certainly interested in discussing it. Mark From: Andrew Kluthe To: How to use LiveCode Sent: Monday, 8 July 2013, 16:05 Subject: LiveCode and WebSockets I have been learning a little bit about websockets lately for a project and I have never really played around with livecode's socket communication methods. This makes me curious. Is there anyone else on the list that might be more familiar with both that would be interested in discussing using something like socket.io as part of a backend for livecode desktop applications? -- Regards, Andrew Kluthe and...@ctech.me ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- Pierre Sahores mobile : 06 03 95 77 70 www.sahores-conseil.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- Phil Davis ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and WebSockets
FYI, there is a mobile sockets plugin being developed by Monte at the moment. The first beta has been in our hands for a couple of weeks. Sockets are fun, and very involved. You are the one implementing the protocols. Sometimes that's exactly what you need, and other times, it's extra work you weren't planning on. I think one of the things you will run into is that we do not have a good way to launch and manage secondary processes, yet. You might be better off to have your socket goodies running in livecode server, or in a separate instance of LC so that you have an easier time keeping all the communication, etc. straight. On Mon, Jul 8, 2013 at 2:51 PM, Andrew Kluthe wrote: > >>However, we don't have proper sockets support on mobile (without > externals at least) > > I am mainly interested in desktop apps at the moment simply because we are > doing most of our mobile apps as mobile web apps. > > However, this will change likely in the next few years if we were to see > sockets and UI (resolution independence, etc) improvements on mobile. > > > >>and websockets are very definitely not the same thing as standard > sockets. > > I am having a hard time just finding straight forward info on the lower > level websocket information. As of right now all the information I am > finding is how to use websockets within this framework or that framework > and nothing really about the differences between websockets and standard > sockets. > > Also, socket programming in general (and in livecode) is new to me because > up until now I have wrote most of my applications using http interfaces. > Not having a non-blocking http client is really getting in the way of some > of the things I want to do with livecode and I really would like realtime > notifications, broadcasting, etc. > > Would you care to discuss the difference between websockets and the sockets > we work with in livecode or point me to some basic information on the > websocket implementation you think we could implement in pure livecode? > What things would keep it from working very efficiently? > > Thanks for taking the time to respond, > > Andrew > > > On Mon, Jul 8, 2013 at 1:35 PM, Mark Wilcox > wrote: > > > We know, I'm interested in websockets for realtime comms between apps. > > Right now I think it'd be possible to implement one or more of the > > supported transports for socket.io in pure LiveCode but maybe not very > > efficiently. An alternative would be to wrap existing native > > implementations as externals. I've not looked into it in any great depth > as > > I'm basically waiting for the engine refactoring to be completed before > > trying to hook new stuff in. > > > > Pierre Sahores wrote: > > > > >The HTTP(S) REST architecture is full supported on any LC desktop or > > mobile platform, iOS and Android included. They can be set to act as > > clients of any kind of nTier server side application (LC-Server, PHP, > RoR, > > etc...). > > > > > >Le 8 juil. 2013 à 18:19, Mark Wilcox a écrit : > > > > > >> I'm interested in using something like socket.io as part of a backend > > for mobile (and maybe also desktop) apps. However, we don't have proper > > sockets support on mobile (without externals at least) and websockets are > > very definitely not the same thing as standard sockets. > > >> > > >> What do you have in mind? I'm certainly interested in discussing it. > > >> > > >> Mark > > >> > > >> > > >> > > >> From: Andrew Kluthe > > >> To: How to use LiveCode > > >> Sent: Monday, 8 July 2013, 16:05 > > >> Subject: LiveCode and WebSockets > > >> > > >> > > >> I have been learning a little bit about websockets lately for a > project > > and > > >> I have never really played around with livecode's socket communication > > >> methods. This makes me curious. > > >> > > >> Is there anyone else on the list that might be more familiar with both > > that > > >> would be interested in discussing using something like socket.io as > > part of > > >> a backend for livecode desktop applications? > > >> > > >> > > >> -- > > >> Regards, > > >> > > >> Andrew Kluthe > > >> and...@ctech.me > > >> ___ > > >> use-livecode mailing list > > >> use-livecode@lists.runre
Re: LiveCode and WebSockets
>>However, we don't have proper sockets support on mobile (without externals at least) I am mainly interested in desktop apps at the moment simply because we are doing most of our mobile apps as mobile web apps. However, this will change likely in the next few years if we were to see sockets and UI (resolution independence, etc) improvements on mobile. >>and websockets are very definitely not the same thing as standard sockets. I am having a hard time just finding straight forward info on the lower level websocket information. As of right now all the information I am finding is how to use websockets within this framework or that framework and nothing really about the differences between websockets and standard sockets. Also, socket programming in general (and in livecode) is new to me because up until now I have wrote most of my applications using http interfaces. Not having a non-blocking http client is really getting in the way of some of the things I want to do with livecode and I really would like realtime notifications, broadcasting, etc. Would you care to discuss the difference between websockets and the sockets we work with in livecode or point me to some basic information on the websocket implementation you think we could implement in pure livecode? What things would keep it from working very efficiently? Thanks for taking the time to respond, Andrew On Mon, Jul 8, 2013 at 1:35 PM, Mark Wilcox wrote: > We know, I'm interested in websockets for realtime comms between apps. > Right now I think it'd be possible to implement one or more of the > supported transports for socket.io in pure LiveCode but maybe not very > efficiently. An alternative would be to wrap existing native > implementations as externals. I've not looked into it in any great depth as > I'm basically waiting for the engine refactoring to be completed before > trying to hook new stuff in. > > Pierre Sahores wrote: > > >The HTTP(S) REST architecture is full supported on any LC desktop or > mobile platform, iOS and Android included. They can be set to act as > clients of any kind of nTier server side application (LC-Server, PHP, RoR, > etc...). > > > >Le 8 juil. 2013 à 18:19, Mark Wilcox a écrit : > > > >> I'm interested in using something like socket.io as part of a backend > for mobile (and maybe also desktop) apps. However, we don't have proper > sockets support on mobile (without externals at least) and websockets are > very definitely not the same thing as standard sockets. > >> > >> What do you have in mind? I'm certainly interested in discussing it. > >> > >> Mark > >> > >> > >> > >> From: Andrew Kluthe > >> To: How to use LiveCode > >> Sent: Monday, 8 July 2013, 16:05 > >> Subject: LiveCode and WebSockets > >> > >> > >> I have been learning a little bit about websockets lately for a project > and > >> I have never really played around with livecode's socket communication > >> methods. This makes me curious. > >> > >> Is there anyone else on the list that might be more familiar with both > that > >> would be interested in discussing using something like socket.io as > part of > >> a backend for livecode desktop applications? > >> > >> > >> -- > >> Regards, > >> > >> Andrew Kluthe > >> and...@ctech.me > >> ___ > >> use-livecode mailing list > >> use-livecode@lists.runrev.com > >> Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > >> http://lists.runrev.com/mailman/listinfo/use-livecode > >> ___ > >> use-livecode mailing list > >> use-livecode@lists.runrev.com > >> Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > >> http://lists.runrev.com/mailman/listinfo/use-livecode > > > >-- > >Pierre Sahores > >mobile : 06 03 95 77 70 > >www.sahores-conseil.com > > > > > >___ > >use-livecode mailing list > >use-livecode@lists.runrev.com > >Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > >http://lists.runrev.com/mailman/listinfo/use-livecode > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- Regards, Andrew Kluthe and...@ctech.me ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and WebSockets
We know, I'm interested in websockets for realtime comms between apps. Right now I think it'd be possible to implement one or more of the supported transports for socket.io in pure LiveCode but maybe not very efficiently. An alternative would be to wrap existing native implementations as externals. I've not looked into it in any great depth as I'm basically waiting for the engine refactoring to be completed before trying to hook new stuff in. Pierre Sahores wrote: >The HTTP(S) REST architecture is full supported on any LC desktop or mobile >platform, iOS and Android included. They can be set to act as clients of any >kind of nTier server side application (LC-Server, PHP, RoR, etc...). > >Le 8 juil. 2013 à 18:19, Mark Wilcox a écrit : > >> I'm interested in using something like socket.io as part of a backend for >> mobile (and maybe also desktop) apps. However, we don't have proper sockets >> support on mobile (without externals at least) and websockets are very >> definitely not the same thing as standard sockets. >> >> What do you have in mind? I'm certainly interested in discussing it. >> >> Mark >> >> >> ________ >> From: Andrew Kluthe >> To: How to use LiveCode >> Sent: Monday, 8 July 2013, 16:05 >> Subject: LiveCode and WebSockets >> >> >> I have been learning a little bit about websockets lately for a project and >> I have never really played around with livecode's socket communication >> methods. This makes me curious. >> >> Is there anyone else on the list that might be more familiar with both that >> would be interested in discussing using something like socket.io as part of >> a backend for livecode desktop applications? >> >> >> -- >> Regards, >> >> Andrew Kluthe >> and...@ctech.me >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > >-- >Pierre Sahores >mobile : 06 03 95 77 70 >www.sahores-conseil.com > > >___ >use-livecode mailing list >use-livecode@lists.runrev.com >Please visit this url to subscribe, unsubscribe and manage your subscription >preferences: >http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and WebSockets
The HTTP(S) REST architecture is full supported on any LC desktop or mobile platform, iOS and Android included. They can be set to act as clients of any kind of nTier server side application (LC-Server, PHP, RoR, etc...). Le 8 juil. 2013 à 18:19, Mark Wilcox a écrit : > I'm interested in using something like socket.io as part of a backend for > mobile (and maybe also desktop) apps. However, we don't have proper sockets > support on mobile (without externals at least) and websockets are very > definitely not the same thing as standard sockets. > > What do you have in mind? I'm certainly interested in discussing it. > > Mark > > > > From: Andrew Kluthe > To: How to use LiveCode > Sent: Monday, 8 July 2013, 16:05 > Subject: LiveCode and WebSockets > > > I have been learning a little bit about websockets lately for a project and > I have never really played around with livecode's socket communication > methods. This makes me curious. > > Is there anyone else on the list that might be more familiar with both that > would be interested in discussing using something like socket.io as part of > a backend for livecode desktop applications? > > > -- > Regards, > > Andrew Kluthe > and...@ctech.me > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode -- Pierre Sahores mobile : 06 03 95 77 70 www.sahores-conseil.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: LiveCode and WebSockets
I'm interested in using something like socket.io as part of a backend for mobile (and maybe also desktop) apps. However, we don't have proper sockets support on mobile (without externals at least) and websockets are very definitely not the same thing as standard sockets. What do you have in mind? I'm certainly interested in discussing it. Mark From: Andrew Kluthe To: How to use LiveCode Sent: Monday, 8 July 2013, 16:05 Subject: LiveCode and WebSockets I have been learning a little bit about websockets lately for a project and I have never really played around with livecode's socket communication methods. This makes me curious. Is there anyone else on the list that might be more familiar with both that would be interested in discussing using something like socket.io as part of a backend for livecode desktop applications? -- Regards, Andrew Kluthe and...@ctech.me ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
LiveCode and WebSockets
I have been learning a little bit about websockets lately for a project and I have never really played around with livecode's socket communication methods. This makes me curious. Is there anyone else on the list that might be more familiar with both that would be interested in discussing using something like socket.io as part of a backend for livecode desktop applications? -- Regards, Andrew Kluthe and...@ctech.me ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
