Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of jlewis@silverhawk.net
 designates 209.85.192.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABBUQ-xs9EM-0kSy7XyX7P+SPQLLK8iO2WG2uyAg-tBVLHWFag@mail.gmail.com>
References: 
 <CAGB5hB12bB46L8mU_zLZ9-W_8dZ64NAvPiRk3yW607rCJhAMCg@mail.gmail.com>
	<CABBUQ-xs9EM-0kSy7XyX7P+SPQLLK8iO2WG2uyAg-tBVLHWFag@mail.gmail.com>
Date: Fri, 9 Jan 2015 10:37:05 -0700
Message-ID: 
 <CABBUQ-z6WNCj==3ewTbvwUuOnwJGJB0ByJyjvn5_j25JS0qwfg@mail.gmail.com>
Subject: Re: A web based terminal emulator as an Apache module?
From: Joe Lewis <jlewis@silverhawk.net>
To: "modules-dev@httpd.apache.org" <modules-dev@httpd.apache.org>
Content-Type: multipart/alternative; boundary=047d7bf0e73cec89d7050c3b9a47

--047d7bf0e73cec89d7050c3b9a47
Content-Type: text/plain; charset=UTF-8

Here is a good example thread :

http://grokbase.com/t/apache/modules-dev/11bp9bhxr5/basic-example-shared-memory-code

On Fri, Jan 9, 2015 at 10:35 AM, Joe Lewis <jlewis@silverhawk.net> wrote:

> It is definitely possible to share information - see the apr_shm_*
> functions (or check the history on this list for shared memory).  Eash POST
> request is considered a separate event, and is processed as such, which
> means there is no state in the protocol itself (there is when you add HTTP
> headers into the mix, such as "cookies").
>
> For what you are trying to do - I'd simply assume it's stateless, and
> design any modules to utilize shared memory.
>
> Joe
>
> On Fri, Jan 9, 2015 at 9:30 AM, Sean Neeley <sean.neeley@producepro.com>
> wrote:
>
>> I'm trying to determine if it is plausible to build an apache module for a
>> web based terminal emulator.  I would be borrowing some of the code from
>> the ShellInaBox project:
>> https://code.google.com/p/shellinabox/
>> The code uses openpty() to create a new process operating in a pseudo-tty.
>> The apache module would have to pass keyboard and display information back
>> and forth from the client browser to the pseudo-tty in the module.
>>
>> It seems like with the pre-fork mpm, I cannot guarantee that the ajax POST
>> requests will make it to the same module instance each time.  Are modules
>> stateless?  Is it possible to share the pseudo-tty and hashmaps keeping
>> session information across all instances of my module?  Or is there
>> anything that can be added to the POST request to guarantee that it goes
>> to
>> a specific module instance?
>>
>> Thanks for the help.
>>
>> - Sean
>>
>
>

--047d7bf0e73cec89d7050c3b9a47--