LDAP V3 server in erlang?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

LDAP V3 server in erlang?

Ranjeet Sonone
I read few messages in the archive regarding LDAP server and client
implementation
based on mnesia. Some more "input/progress info/code" on the same would he
really
helpful. I am willing to contribute to the effort if proves helpful.

thanks and regards,
-ranjeet



Reply | Threaded
Open this post in threaded view
|

LDAP V3 server in erlang?

tobbe
I implemented an LDAPv3 client package, which later
Sean Hinde started to transformed into a gen_fsm form.
However, some of my intentions was lost in the trasnformation
so my plan was to modify the the gen_fsm version to
my liking. Haven't had the time to do that yet though...

Anyway, you'll find the current code here:

 http://www.bluetail.com/~tobbe/eldap.tgz

Cheers /Tobbe


>From Sean.Hinde  Mon 30 Jul 16:35:27 2001
Return-Path: <owner-erlang-questions>
Received: (from majordom)
          by hades.cslab.ericsson.net (8.10.0/8.10.0/hades-1.2) id f6UEcQ127593
          for erlang-questions-outgoing; Mon, 30 Jul 2001 16:38:26 +0200 (CEST)
Received: from o2ogate.one2one.co.uk (o2ogate.one2one.co.uk [193.131.126.162])
          by hades.cslab.ericsson.net (8.10.0/8.10.0/hades-1.2) with ESMTP id f6UEcKi27588
          for <erlang-questions>; Mon, 30 Jul 2001 16:38:21 +0200 (CEST)
Received: from kitts.one2one.co.uk (kitts.one2one.co.uk [149.254.74.217])
          by o2ogate.one2one.co.uk (8.9.3/8.9.3) with ESMTP id PAA11771;
          Mon, 30 Jul 2001 15:37:55 +0100 (BST)
Received: from mailhost.one2one.co.uk (localhost [127.0.0.1])
          by kitts.one2one.co.uk (8.9.3/8.9.3) with ESMTP id PAA22991;
          Mon, 30 Jul 2001 15:37:55 +0100 (BST)
Received: from imp01ims.One2One.co.uk (imp01ims [149.254.72.7])
          by mailhost.one2one.co.uk (8.9.3/8.9.3) with ESMTP id PAA25388;
          Mon, 30 Jul 2001 15:37:47 +0100 (BST)
Received: by imp01ims.one2one.co.uk with Internet Mail Service (5.5.2448.0)
          id <3W3KN930>; Mon, 30 Jul 2001 15:35:34 +0100
Message-ID: <402DD461F109D411977E0008C791C312039F61FC>
From: Sean Hinde <Sean.Hinde>
To: Ranjeet Sonone <ranjeet>,
   "'tobbe'"
    <tobbe>
Cc: erlang-questions
Subject: RE: LDAP V3 server in erlang?
Date: Mon, 30 Jul 2001 15:35:27 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
              charset="iso-8859-1"
Sender: owner-erlang-questions
Precedence: bulk

Hi,

Since then I've split up my gen_fsm tcp/ip client thingy into a generic part
which looks after sockets, timers etc, and provides callbacks for the
protocol implementation.

I think it fixes most of your concerns but I haven't ported the eldap stuff
over yet. I'll try to have a go this week and release it..

(BTW Ranjeet, the reason to turn it into a gen_fsm was to be able to have
many threads query over the same LDAP socket connection and have some stuff
to maintain the link - retries and so on)

Rgds,                    
Sean                      
                         
                         

> I implemented an LDAPv3 client package, which later
> Sean Hinde started to transformed into a gen_fsm form.
> However, some of my intentions was lost in the trasnformation
> so my plan was to modify the the gen_fsm version to
> my liking. Haven't had the time to do that yet though...
>
> Anyway, you'll find the current code here:
>
>  http://www.bluetail.com/~tobbe/eldap.tgz
>
> Cheers /Tobbe
>


NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.