From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Changes in libccs behaviour (PLEASE READ!)
Date: Tue, 3 Jun 2008 11:16:11 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0806031055250.5892@trider-g7> (raw)
Hi guys,
I just landed the last bits in libccs to support both xpath lite and full
xpath queries. With this new code, a couple of things need to be checked
across all applications using libccs.
Relevant changes:
ccs_connect() used to return only when cluster is quorated.
This is not the case anymore. ccs_connect will return as soon as it can
connect to aisexec and init properly (or fail).
You can use cman_is_quorate from libcman for the same feature.
ccs_force_connect() used to take a cluster name in input. The API is still
the same, but the cluster name is now ignored (it wasn't in used before
either).
in order to use xpath lite or full xpath, set fullxpath (int from ccs.h)
to either 0 (xpath lite and default) or 1 (full xpath) before invoking
ccs_connect or ccs_force_connect.
In order to switch from one mode to another, you have to disconnect and
connect again.
WARNING: use full xpath only if you cannot live without. It is slow and
it's a memory eating piece of code.
WARNING2: the library is not thread safe (yet?). So far none of our
callers really need this feature. Please let me know if i overlooked.
Please review your ccs init calls around and take appropriate actions.
ccs_test(8): not fully completed yet (another email will follow).
Feel free to contact me if you have any questions
Fabio
PS hint: ccs_force_connect() has a blocking option that will idle loop as
long as required and will exit the loop when cman is available for
queries. This could replace several hand made loops on ccs_connect i have
seen around.
--
I'm going to make him an offer he can't refuse.
next reply other threads:[~2008-06-03 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 9:16 Fabio M. Di Nitto [this message]
2008-06-10 13:19 ` [Cluster-devel] Changes in libccs behaviour (PLEASE READ!) Lon Hohberger
2008-06-10 15:02 ` Fabio M. Di Nitto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0806031055250.5892@trider-g7 \
--to=fdinitto@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).