Calling a livecode executable -ui from LC server and get back a result.

[Ralph DiMola]

I am running my Android Remote Tester LC app as a Windows Service on Win 10. It has a UI for debugging/examining operation when run in the Windows UI and this UI does not cause any problems when running as a service. I just startup up everything in the preopenstack. This app does socket communications for user requests and performs various functions including shelling out to the OS and returning the result back to the client. It's been very reliable while running as a service and has never has any mysterious crashes. This app supports multi user connections. I use the socket address as an index into an array for session context. As it is single threaded, it has to finish one request before it can work on the next but does not have the overhead of starting up a new process for each connection/request. Could this work for you?

Ralph DiMola
IT Director
Evergreen Information Services
rdimola at evergreeninfo.net


-----Original Message-----
From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On Behalf Of Malte Brill via use-livecode
Sent: Friday, May 05, 2017 8:36 AM
To: use-livecode at lists.runrev.com
Cc: Malte Brill
Subject: Re: Calling a livecode executable -ui from LC server and get back a result. 

Hi Roger,

indeed, I have considdered that. But I have no experience on how this would behave. Actually what I was trying to do is reducing the involved components, instead of introducing more and more over the course of building the system. LC - Server came natural there, as it would have allowed me to use liveCode inline and having the proven stability of Apache, which is needed for other purposes in the project also. It is so unfortunate, that LC-server gets me to 95% of what I need to do and then you need to revise your decisions, because some things that you would expect to work, just won’t. I can most certainly move everything that is needed into a liveCode client, but I would not want to do that because of apllication design reasons. Pitty. If I were to set up a faceless app as a service / daemon, I am not too sure if I would do it in LC, given that it would be a single threaded process and I might need concurrency. The pretty part of the CGI approach is that it starts an instance per connection that then can act individually. Well, back to whiteboard I guess.

Thanks a lot,

Malte



> Have you considered running a faceless Desktop app as a service, having it watch for a socket message, or a file, or even clipboard content to signal it to do something. You could keep an account signed in with an app running -with-or-without a UI. 
> 

_______________________________________________
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