Cruz [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 24, 2002 10:18 PM
To: Vinod Panicker
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Re: [PHP] Full-Duplex communication
So still there is nothing in your requirements that doesn't suggest
you'll
do fine with a PHP-based listener.
Of course
So still there is nothing in your requirements that doesn't suggest you'll
do fine with a PHP-based listener.
Of course you have the memory overhead of the PHP interpreter's RAM
infrastructure multiplied by the number of simultaneous connections, but
that would be the same with Apache (at
Hi Evan,
What you said did make sense, and complements my knowledge of
sockets.
But what i'm not sure of is this - if i construct my own packet
and send it across, presuming that i do have the ip address and
port number of the client on which it is reading, will the client
accept it as a
Not to be argumentative, but what you're trying to do is just so amazingly
much more complicated than any of my suggestions. Maybe I haven't
communicated it well, it maybe there's some requirement to your project
that I don't understand.
Why not just write a listener in PHP and redirect to it?
LOL.. I like the color red BTW.
Let me explain my project more in detail.
This system is an Instant messaging system, with the backed
running on apache / php / mysql. The front end client is a COM
component that communicates with the backend, and interfaces with
an MFC app.
Now since
Vinod,
Interesting...
Okay unless I'm mistaken, what you want to do can't be accomplished through
PHP. However, you may want to take a look at libnet.
http://www.packetfactory.net/Projects/Libnet/
I've always wanted someone to create a PHP interface for this- unfortunatly my
C isn't quite
I don't think you're going to get Apache to hand you the socket.
However, you can write a program using the standalone (CGI) PHP
interpreter that will act like a server - check out
http://php.net/socket_create_listen for more info.
You could redirect from your standard web server to your
1st thing: sorry about the double-post. i don't know why that happened. If
this one gets double posted too, i apologize in advance.
2nd: php.net/pcntl
On Tuesday 21 May 2002 23:30 pm, Miguel Cruz wrote:
I don't think you're going to get Apache to hand you the socket.
However, you can
Ah, yes - http://php.net/pcntl_fork
Well there you go, then - everything required to create a server in PHP.
miguel
On Tue, 21 May 2002, Evan Nemerson wrote:
1st thing: sorry about the double-post. i don't know why that happened. If
this one gets double posted too, i apologize in advance.
Thanks for the reply Miguel, but here i'm not trying to implement
my own multi-threaded server - exactly the reason why i'm using
Apache / PHP.
I could have made a listening server which is based on a
multi-threaded or multi-forked model, but the time and
complexities involved would be huge.
At 5:55 AM + 22/5/02, Vinod Panicker wrote:
I want the ability to write to a socket thats been created earlier
- i want to steal it from Apache, so that i can use it when and
where i like.
Why not just keep your script running and have it send more data
to the browser whenever it becomes
What i have at the other end is a Instant Messenger client :)
Cant have the script running till the time the user logs out can
i? And also, different activities are triggered on the server
asynchronously (presence status, instant messages, notifications)
which has to be sent to the client.
At 7:01 AM + 22/5/02, Vinod Panicker wrote:
What i have at the other end is a Instant Messenger client :)
Which is presumably accepting some form of HTML or at least a
stream of data sent over HTTP and displaying the data. If it's
notdoing this, Apache is almost certainly the wrong
Hi Richard,
Thanks for your suggestion.
Yes, Apache is the wrong platform for the server. What would be
ideal is a custom designed TCP based multi-threaded server.
Since we had lots of constraints, we went in for Apache / PHP.
What i'm trying to do is to reduce the number of compromises
On 22 May 2002, Vinod Panicker wrote:
Instant is how the response should be. Thats why i'm clamouring
for the socket so that i can send data directly to the client,
from a C++ binary or maybe another script.
If you're willing to write C code, I'd suggest posing your question in
On Wed, 22 May 2002, Miguel Cruz wrote:
On 22 May 2002, Vinod Panicker wrote:
Instant is how the response should be. Thats why i'm clamouring
for the socket so that i can send data directly to the client,
from a C++ binary or maybe another script.
If you're willing to write C code, I'd
Just subscribed to comp.infosystems
True, the listen-fork model would hardly be any lines of code, but
the changes that will have to be done to the client and the server
would be enormous. We are talking abt a production system here
which needs to be optimised. I cant honestly go ahead
You're right- this is getting interesting ;)
http://www.packetfactory.net/libnet/manual/4.html#s4.1.5
Unless I'm mistaken, you don't need to actually hijack the socket- you merely
need to write to the network. Check out section 3.1 of RFC 793. There is
source and destination port- that is how
Hi,
We have developed a client-server application where the server
needs to send asynchronous data to the client. Now since we are
using Apache/PHP/MySQL, the client needs to poll the server
periodically for information.
I was thinking if there was some way to get around this basic
Hi!
I'm looking for an answer to your questions as well, so if you do find a
solution on other lists, could you please post it here as well?
Regarding the issue, your proposal wouldn't make for full-duplex as far
as I understand since I don't see how the client would be able to send
any data
Hi,
Tx for your very prompt reply.
Yeah, I'll post the solution as soon as I find it someplace.
Let me outline the problem in more detail -
Client (VC++) calls a PHP script on the server, specifies the
connection type as Keep-Alive. The PHP script, somehow (still a
big question) gets the
For your specific problem, I think Mr. Lemos has provided a viable
solution (using print() or echo() and flush() whenever you need to,
instead of grabbing the socket and write() to it). My problem however is
how you envision solving the communication the other way around (i.e.
when the CLIENT
Hi,
It still seems like I havent made the problem clear enough.
I am aware of the print(), echo() and flush() functions and what
they do. It does not fit in as a solution. Let me explain my
problem more elaborately -
The client calls a PHP script, script_a.php on the Apache web
server,
23 matches
Mail list logo
