yes, those are the requirements. anyways i have gone with writting my own
message queue with a thread that sees if its full or not so send it away
On Thu, Dec 6, 2012 at 7:51 PM, Josh Cartmell wrote:
> Why not use the same database? i.e. is there any reason that they have
> to have separate dat
Why not use the same database? i.e. is there any reason that they have
to have separate databases?
On Dec 6, 5:10 am, psychok7 wrote:
> Thanks for the answer.. but what I. Could have synchronous replication? What
> do you advise over a rest interface?
--
You received this message because you a
Thanks for the answer.. but what I. Could have synchronous replication? What do
you advise over a rest interface?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-u
If you're not using synchronous replication (ie, something like a two-phase
commit, or something very close to it), then it is impossible to come up
with a generic solution for replication. you might be able to "come close",
but how to deal with desync is application specific.
Ie, say you had t
So I have this 2 applications connected with a REST API (json messages).
One written in Django and the other in Php. I have an exact database
replica on both sides (using mysql).
My question is, how can i keep this 2 applications databases synchronized?
In other words, when i press "submit" o
5 matches
Mail list logo
