often visit use.perl, perl news, but I only got some rumours in
this list, no fact or official announcements.
Please smebody tell me what's going on nowadays!
Thanks, and keep up your _definitely good_ work :-)
dLux
--
thread-switch to our thread will continue to release
the locks until all the locks are released.
I still think that we can implement this in a quite simple way IF we
assume we already designed our perl interpreter to thread-safe.
If you still have objections, share with us!
dLux
--
(separated .so for the thread handling), then it means
minimal overhead (some more callback call, and that's all).
Are you satisfied with this? I think this is a good compromise, and
still powerful :-)
\---
dLux
--
#!/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$
s
to be implemented in the core, and this is not more than the 2pc
alg.
\---
dLux
--
This Message is Powered by VI
/--- On Mon, Sep 04, 2000 at 07:18:56PM -0500, Greg Rollins wrote:
| Will perl monitor the commit and rollback actions of transactions?
\---
What exactly you mean?
dLux
--
This message is READ-ONLY
MVCC) like in postgreSQL
If we forget about the MVCC, then all things are very
straightforward, aren't they? It is _not_ complicated at all. It is
all Perlish!
\---
dLux
--
Szab, Balzs Tibor - dLux - HuLUG - Allinphos
( mailto:[EMAIL PROTECTED] http://www.d
cleanings, because it is still not functional in this state (I need
some time to write a new version of the RFC), but I think this is
the future! Look at the Object interface and TIE interface in the
RFC.
Has anybody got other idea to manage transactions outside perl, and
how it can
?
Tied interface transaction-enable can be good, belive me!
dLux
--
... Vgy egy Magnumot s fogd r a Nyuszira!
strange results when using a versioned tied
variable.
That's why I thought versioning and more intelligent locking has
quite a lot overhead.
\---
dLux
--
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc
