Ldap.Client.Delete

Delete operation.

This operation comes in four flavours:

• synchronous, exception throwing (delete)
• synchronous, returning Either ResponseError () (deleteEither)
• asynchronous, IO based (deleteAsync)
• asynchronous, STM based (deleteAsyncSTM)

Of those, the first one (delete) is probably the most useful for the typical usecase.

Documentation

delete :: Ldap -> Dn -> IO ()

Perform the Delete operation synchronously. Raises ResponseError on failures.

deleteEither :: Ldap -> Dn -> IO (Either ResponseError ())

Perform the Delete operation synchronously. Returns Left e where e is a ResponseError on failures.

deleteAsync :: Ldap -> Dn -> IO (Async ())

Perform the Delete operation asynchronously. Call wait to wait for its completion.

deleteAsyncSTM :: Ldap -> Dn -> STM (Async ())

Perform the Delete operation asynchronously.

Don't wait for its completion (with waitSTM) in the same transaction you've performed it in.

data Async a

Asynchronous LDAP operation. Use wait or waitSTM to wait for its completion.

Instances

Functor Async

Defined in Ldap.Client.Internal

Methods

fmap :: (a -> b) -> Async a -> Async b

(<$) :: a -> Async b -> Async a

wait :: Async a -> IO (Either ResponseError a)

Wait for operation completion.

waitSTM :: Async a -> STM (Either ResponseError a)

Wait for operation completion inside STM.

Do not use this inside the same STM transaction the operation was requested in! To give LDAP the chance to respond to it that transaction should commit. After that, applying waitSTM to the corresponding Async starts to make sense.