Home > Archive > LDAP > August 2005 > faking atomic transactions in Net::LDAP
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
faking atomic transactions in Net::LDAP
|
|
| Mike Whitaker 2005-08-02, 9:21 am |
| ....and fully expecting the answer 'you can't, Mike'.
I have two Net::LDAP::Entry's, which I would like, if possible, to
call $entry->update without something being able to sneak in the gap
between them and grab out of sync data.
Any suggestions? My current horrid hack idea is to convert 'em to
LDIF and spawn ldapadd :)
| |
| Chris Ridd 2005-08-02, 9:21 am |
| On 2/8/05 1:56, Mike Whitaker <mike@mindcandydesign.com> wrote:
> ...and fully expecting the answer 'you can't, Mike'.
>
> I have two Net::LDAP::Entry's, which I would like, if possible, to
> call $entry->update without something being able to sneak in the gap
> between them and grab out of sync data.
>
> Any suggestions? My current horrid hack idea is to convert 'em to
> LDIF and spawn ldapadd :)
You can't do it. Your horrid hack won't work either, because it just ends up
sending two add operations in protocol.
I think there are some (expired) internet drafts around which describe how
to implement transactions, but you'll have to look quite hard for servers
which implement them :-(
Cheers,
Chris
| |
| Mike Whitaker 2005-08-02, 9:21 am |
| >> Any suggestions? My current horrid hack idea is to convert 'em to
>
> You can't do it. Your horrid hack won't work either, because it
> just ends up
> sending two add operations in protocol.
That's rather what I suspected. Ah, well.
Thanks anyway. :)
|
|
|
|
|