On Mon, Dec 03, 2007 at 04:24:51AM -0500, Daniel Veillard wrote:
On Fri, Nov 30, 2007 at 10:32:40PM +, Daniel P. Berrange wrote:
On Thu, Nov 29, 2007 at 05:16:34PM +, Daniel P. Berrange wrote:
This patch hooks up the basic authentication RPC calls, and the specific
SASL
On Fri, Nov 30, 2007 at 10:32:40PM +, Daniel P. Berrange wrote:
On Thu, Nov 29, 2007 at 05:16:34PM +, Daniel P. Berrange wrote:
This patch hooks up the basic authentication RPC calls, and the specific
SASL implementation. The SASL impl can be enabled/disable via the configurre
Daniel P. Berrange [EMAIL PROTECTED] wrote:
On Thu, Nov 29, 2007 at 02:43:09PM -0500, Daniel Veillard wrote:
...
I know, I have also argued against it (and that's why libxml2 doesn't
parse it), but this can be way more convenient at times, and also
has the potential to remove asynchronous
On Thu, Nov 29, 2007 at 05:16:34PM +, Daniel P. Berrange wrote:
This patch hooks up the basic authentication RPC calls, and the specific
SASL implementation. The SASL impl can be enabled/disable via the configurre
script with --without-sasl / --with-sasl - it'll auto-enable it if it finds
On Thu, Nov 29, 2007 at 01:08:52PM -0500, Daniel Veillard wrote:
On Thu, Nov 29, 2007 at 05:16:34PM +, Daniel P. Berrange wrote:
This patch hooks up the basic authentication RPC calls, and the specific
SASL implementation. The SASL impl can be enabled/disable via the configurre
script
On Thu, Nov 29, 2007 at 07:20:08PM +, Daniel P. Berrange wrote:
Actually there we should looks for a password and store it, that's very
common and convenient, e.g. use
xen://foo:[EMAIL PROTECTED]/
as the connection URI, libxml2 will just return the user as 'foo:bar'
which
On Thu, Nov 29, 2007 at 02:43:09PM -0500, Daniel Veillard wrote:
On Thu, Nov 29, 2007 at 07:20:08PM +, Daniel P. Berrange wrote:
Actually there we should looks for a password and store it, that's very
common and convenient, e.g. use
xen://foo:[EMAIL PROTECTED]/
as the
Hi Dan
I haven't used getnameinfo much, so looked it up and found this:
In order to assist the programmer in choosing reasonable sizes for the
supplied buffers, netdb.h defines the constants
# define NI_MAXHOST 1025
# define NI_MAXSERV 32
Daniel
On Thu, Nov 29, 2007 at 09:31:50PM +0100, Jim Meyering wrote:
Hi Dan
I haven't used getnameinfo much, so looked it up and found this:
In order to assist the programmer in choosing reasonable sizes for the
supplied buffers, netdb.h defines the constants
#
