FWIW I've just built the branch and attached the jars to this email - so
you can use them right now and don't have to build it yourself. Below is
also a little bit written about the current status of plain SASL.
First, the config for membase buckets looks like this:
The memcachedNodes can also take multiple uris, e.g.
Plain SASL is used when the memcachedNodes are configured as before
(here without nodeIds) and username + password are specified, e.g.:
I just noticed that when memcachedNodes with nodeIds (e.g.
memcachedNodes="n1:localhost:11211,n2:localhost:11212) are configured no
authentication will be done, so SASL is not available in this combination.
AFAICS with heroku you have only a single memcached instance available
so there it seems not be an issue. Apart from that I'd say it should be
possible to use multiple memcacheds and SASL.
Any opinions an that?
Btw, the connectionType attribute that was part of the original pull
request is no longer used as the connection type (membase, SASL,
default) is concluded from the configuration settings.
On 12/13/2011 11:44 PM, Martin Grotzke wrote:
sorry for the slow progress during the last weeks - my day job took all
the time (also nights ;-)).
Short answer: I'm going to release msm with membase support this year.
More words: The membase stuff is finished and unit/integration tested,
I'm only waiting for the couchbase guys to push an updated CouchbaseMock
version with my contributed changes used for integration testing of this
membase/SASL functionality. If they don't take action I'll publish the
version in my own maven repo.
Besides that I'm currently working on issue 111  ("Concurrent
requests for a non-sticky session w/o session locking on the same tomcat
may interfere") and I wanted to have this fixed in the upcoming release.
However there are some subtle difficulties I'm fighting with so perhaps
it won't make it into the release - we'll see.
Btw.: a time consuming part of a release is final testing, updating
docs, release notes etc. If any of you guys is willing to help with this
(or even more, coding, you know :-)), I'd really be happy!
Thanx for your patience,
On 12/12/2011 09:10 PM, pradeep gummi wrote:
+1 vote to be merged into the master. We did basic functional testing in
our webapp with SASL dev version and it looked good to us and are in the
process of deploying this to production.
On Mon, Dec 12, 2011 at 1:24 PM, Scott Clasen <email@example.com
Is there any timeline on when the memcached-sasl branch might be
merged into master and released.
This would allow the memcached session manager to be used on heroku
apps that use the memcached addon provided by couchbase, and