LC Server & Server Based Stack?

[Mike Bonner]

It was mostly in response to having lc (in cgi mode) talk to a different
(non-http connected) process.

On Sun, Jan 8, 2017 at 10:32 PM, Phil Davis via use-livecode <
use-livecode at lists.runrev.com> wrote:

> Hi Mike,
>
> It sounds like you're talking about things that apply when your server
> stack is used in a long-running LC process. If you run in CGI mode, you
> don't have to deal with some of those things (like figuring out when to
> reload a stack). Personally I'm glad the on-rev default is CGI mode.
>
> Best -
> Phil Davis
>
>
>
>
> On 1/8/17 7:26 PM, Mike Bonner via use-livecode wrote:
>
>> Sorry I didn't get back to you till now, but it looks like things are
>> covered as far as accessing a stack file from lc server.  As for the other
>> direction, (lc server talking to an in memory stack..)  FROM the stack
>> itself would be a simple http request, but the reverse not so much.
>>
>> I'm now curious though.  If one were to change an lc stack file, and have
>> your executing stack look for an updated timestamp ever so often, you
>> could
>> have it unload the old version, and reload the freshly updated one for
>> processing possibly.  Though it would probably be simpler to have lc
>> server
>> write to a file and just load whatever new data from the file with the
>> stack.
>>
>> Or, if the stack doesn't need to be running all the time, lc server could
>> shell call the stack executable (perhaps a simple stackrunner) that would
>> take an external stackfile name as a parameter to do whatever it is you
>> need to do.
>>
>> Also, depending on what you need to do, the httpd stack by andre garzia is
>> pretty awesome.  (it would bipass the need for lc server, but is single
>> threaded so might not be appropriate for some things)    Its been a while
>> since I messed with it, but when I did, I set up an android app that took
>> in swipes and clicks and sent the information to the httpd  stack (and at
>> the time I had managed to build a "click" external.. its probably here
>> somewhere).. basically i had a home brew computer remote control app that
>> was incredibly simple to build, and worked great.  If it fits your use
>> case, that httpd stack is awesome.
>>
>> On Sun, Jan 8, 2017 at 6:39 PM, Rick Harrison via use-livecode <
>> use-livecode at lists.runrev.com> wrote:
>>
>> Hi Stephen, Phil, & Jacque,
>>>
>>> Thanks for the info!  I’ll get back to you after studying this stuff.
>>>
>>> Rick
>>>
>>> On Jan 8, 2017, at 3:42 PM, Stephen Barncard via use-livecode <
>>>>
>>> use-livecode at lists.runrev.com> wrote:
>>>
>>>> some stack use info as used in web app RevIgniter:
>>>>
>>>> https://revigniter.com/userGuide/general/using_stacks.html
>>>>
>>>> by the way, RevIgniter is a self-contained framework that you might find
>>>> useful for all kinds of web development in livecode.
>>>>
>>>> It might be a little different than your own programming style, but John
>>>> Craig's creation is a living example of the "Model-View-Controller"
>>>>
>>> concept.
>>>
>>>> --
>>>> Stephen Barncard - Sebastopol Ca. USA -
>>>> mixstream.org
>>>>
>>>> On Sun, Jan 8, 2017 at 12:34 PM, Stephen Barncard <stephen at barncard.com
>>>> >
>>>> wrote:
>>>>
>>>> here's some basics from the docs
>>>>>
>>>>> http://lessons.livecode.com/m/4070/l/36656-how-do-i-use-
>>>>> stacks-with-livecode-server
>>>>>
>>>>> --
>>>>> Stephen Barncard - Sebastopol Ca. USA -
>>>>> mixstream.org
>>>>>
>>>>> On Sun, Jan 8, 2017 at 12:17 PM, Rick Harrison via use-livecode <
>>>>> use-livecode at lists.runrev.com> wrote:
>>>>>
>>>>> Hi Stephen,
>>>>>>
>>>>>> That sounds promising.. do you know of any good examples?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Rick
>>>>>>
>>>>>> On Jan 8, 2017, at 3:12 PM, Stephen Barncard via use-livecode <
>>>>>>>
>>>>>> use-livecode at lists.runrev.com> wrote:
>>>>>>
>>>>>>> stacks are great with LC server. For instance, one can use custom
>>>>>>> properties and libraries just by 'start using' that stack.
>>>>>>>
>>>>>>> I'm not sure about fields but I think they are accessible too.
>>>>>>>
>>>>>>> And one can test and edit everything 'on the ground' first.
>>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>> 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
>>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>> _______________________________________________
>> 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
>>
>
> --
> Phil Davis
>
>
>
> _______________________________________________
> 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
>