David,
I think you're right. I've been playing with this in my sandbox of 2
computers and a 4D server. Even with an ABORT command the web process seems
to die but then, Hydra like, spring back into existence.

What I'm trying to do is implement a new chat module I've made. Since the
actual chat mechanics are handled by another web service (Pubnub people,
really) I just need to launch the page. For intra-4D comms I was playing
with a web area that loads the page from disk. But this doesn't seem to
mesh well with the web service. So initiating each client with a call to
the web server seems to work great. My concern is a bunch of web processes
that only serve to startup these chat pages persisting. But I suppose I
could let 4D web server - I dunno, be the web server and deal with it.
Persisting variables aren't an issue as the only ones that matter are
populated from the query string.

Now the issue seems to be you can't open a web area to a link from the web
server of the 4D server. I knew you couldn't (or shouldn't) try that with a
web area on the same machine as the web server but I didn't expect it would
be an issue to a machine with a different IP.

It's actually easier to just open the page in a browser. But then there's
the issue of having a chat minimized and 4D opening another browser window
onto the same chat instead of being able to recognize the window(process)
it already has open for those same chat members.

On Mon, May 1, 2017 at 7:14 PM, David Adams via 4D_Tech <
[email protected]> wrote:

> By the way, I don't think that there is a way for your to kill a Web
> ​ ​
> request anyway...
>


-- 
Kirk Brooks
San Francisco, CA
=======================

*The only thing necessary for the triumph of evil is for good men to do
nothing.*

*- Edmund Burke*
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to