Wow. That pretty much sums it up!
I'll probably give the standard sockets another try. I'll report back
on my problems.
> -Original Message-
> From: Richard Lynch [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 28, 2007 4:32 PM
> To: Bob Dusek
>
munication?
> -Original Message-
> From: Richard Lynch [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 28, 2007 4:11 PM
> To: Bob Dusek
> Cc: Robert Cummings; Jay Blanchard; php-general@lists.php.net
> Subject: RE: [PHP] operational musings
>
> Perhaps try j
>From my experience, database replication from the central server to each
of the stores won't scale...
We use a timed (every X minutes), home-brewed protocol that does
something similar to a synchronization. And, we don't synchronize the
entire database at central server (as there are parts of t
The company I work for is currently doing this... using PHP in a retail
environment, with a Linux server in every store, talking to the POS
controller via a socket, storing data in a database (postgres), and
processing retail transactions in real-time. And, sending results of
those transactions to
Hello all,
I've got a program (program X) that does the following:
* opens a socket (socket A)
* binds socket A to an address/port (x.x.x.x/1099)
* then opens another socket (socket B),
* binds socket B to an address/port (x.x.x.x/1100)
* calls listen on socket B
* launches a second program (pr
If you have the timezone offset stored for each contact, you can compare
that to the timezone offset of the server and do the math on a timestamp
value.
// return value format: hhmm
// -0500 for US/EST, -5 hours relative to GMT
$timeZoneOfServer = date("O");
> -Original Message-
> Fro
> > No. We don't need the persistence. I'm planning on
> managing the flow
> > and not sending the data if the app isn't available to
> receive it on the
> > other end.
>
> Will you need to resend?
Nope. Not in-line. We have an off-line message processing procedure to
handle the missed tr
> > So, I'm leaning toward local sockets. I'm implementing
> this right now,
> > so I can test the performance against the Postgres
> implementation. I
> > will also implement and test other solutions if anyone can persuade
> > me... ie. if you feel the msg_get_queue() stuff is worth the
> > c
Hello all,
I'm looking for some advice from people that have experience with
inter-process messaging queues. If you have experience with this sort
of thing, I would appreciate any advice you can give...
I'm working on an application that is extremely performance-sensitive.
And, we're passing a l
Are sockets created via stream_socket_pair more efficient for IPC than
standard socket/port communications?
I want to open a process with proc_open, and I want to use a socket to
for IPC. One solution is to just create a socket in the parent and pass
the port number to the child. Then, when the
10 matches
Mail list logo
