RE: [Fwd: Re: [PEAR-DEV] User authorisation class]

2 more things. 1) The array I mentioned should be passed by reference and any new connections should be also referenced in this array. This way not only existing connections will be reused but also any new connection created by the auth class can be then used by the app. 2) If you want to get this thing going ASAP maybe you should not use XML to define the server lists but just a simple php with an array. Later you can then add the XML server list from which this php array can be generated. This will mean that the auth class does not need to constantly parse an XML file again. Also I don’t know how often some other app really needs to read and/or write to the server list anyways, so I think you don’t need to hurry with XML. Best regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de > -----Original Message----- > From: Markus Wolff [mailto:wolff@21st.de] > Sent: Monday, June 24, 2002 12:07 AM > To: smith@dybnet.de > Cc: rocha@i-node.com.br; pear-dev@lists.php.net > Subject: Re: [Fwd: Re: [PEAR-DEV] User authorisation class] > > Am Sun, 23 Jun 2002 23:52:08 +0200 schrieb "Lukas Smith" > <smith@dybnet.de>: > > > Why not just let the app developer decide? > > If you have the list of servers then you can pass an array with > > connection objects references stored in it. > > > > The keys in the arrays are the names of the container from the server > > list. > > That´s how the array is organized already. I think that at some point, > all of the three mentioned solutions will be possible so the developer > can choose freely. However, this adds complexity which in turn raises > the possibilty for errors - and it is my goal to make a first usable > release ASAP, then make it stable so that it can safely be used in a > production environment and then add all the nice bells and whistles. > > Regards, > Markus > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php