Great! Thanks Dan.
I'll be making a php version of something similar.
Martin
"Dan Joseph" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
>
> > sounds like a good idea. How does 'gateway' actually listen in on the
> > website session?
> >
> > Is it simply invoked by the website
Hi,
> sounds like a good idea. How does 'gateway' actually listen in on the
> website session?
>
> Is it simply invoked by the website with specific arguments?
It has a socket connection that waits for an incoming request from the web
site, and then it takes what was sent from the web sit
Hi Dan,
sounds like a good idea. How does 'gateway' actually listen in on the
website session?
Is it simply invoked by the website with specific arguments?
Tx,
Martin
"Dan Joseph" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
>
> > Quick answer: as others before me have als
Hi Martin,
This is unfortunately not something that has an easy work around. I have
seen a post by Dan Joseph with what looks like a good suggestion.
If my understanding of J2EE is correct, i believe you will be able to
persist connections between two different pages if you use java servlets.
Hi Chris,
yes, that's precisely my problem (I had read the notes).
This seems like something people would want to do, so I'm surprised no one's
found some workaround.
Any other ideas?
"Chris Shiflett" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> --- Martin Helie <[EMAIL PROTEC
Hi,
> Quick answer: as others before me have also mentioned this cannot be done.
> >
> >has anyone found a way to keep a resource handle alive between
> page loads?
> >
I've missed most of this thread, but thought I'd let you know what I'm
going for a socket setup right now. It may or ma
Quick answer: as others before me have also mentioned this cannot be done.
Martin Helie wrote:
Here's a quick one:
has anyone found a way to keep a resource handle alive between page loads?
For example, I open a socket with fsockopen, and I'd like the handle to
survive page loads. As you know,
--- Martin Helie <[EMAIL PROTECTED]> wrote:
> no, unfortunately, that doesn't work; it creates a permanent socket on
> the server, but between page reads, php still loses its resource id,
> and can't communicate with the socket...
The last two user notes on this page seem relevant:
http://www.php
Hi Chris,
no, unfortunately, that doesn't work; it creates a permanent socket on the
server, but between page reads, php still loses its resource id, and can't
communicate with the socket...
Martin
"Chris Hayes" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> At 16:09 10-11-03, you
At 16:09 10-11-03, you wrote:
Here's a quick one:
has anyone found a way to keep a resource handle alive between page loads?
For example, I open a socket with fsockopen, and I'd like the handle to
survive page loads. As you know, there's not much point storing it in a
session (or its parent objec
Here's a quick one:
has anyone found a way to keep a resource handle alive between page loads?
For example, I open a socket with fsockopen, and I'd like the handle to
survive page loads. As you know, there's not much point storing it in a
session (or its parent object)...
Any ideas?
Tx,
Martin
11 matches
Mail list logo
