On Jul 7, 2004, at 1:22 AM, Rob Cozens wrote:
Solution #4) instead of having the two standalones vie for access to the data stack directly, create a third server standalone that sends data stack data to any requesting standalone(s) and files data in the data stack for them. This completely avoids data collision, and locked record tables can be maintained in the server's RAM. This is the basic design used by SDB.
--
Rob,
that's what I was thinking for solution #2... when I say webserver, I am talking about the revHTTPd project scripts, that enable a stack act as a server... (even serving methods, handlers and data!)
by the way SDB is amazing... I really like it.
Cheers Andre
Rob Cozens CCW, Serendipity Software Company
-- Andre Alves Garzia 2004 Soap Dog Studios - BRAZIL http://studio.soapdog.org
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
