<div dir="ltr">I think we need configuration properties for both Redis and CouchDB. Currently both only take a minimal of the server/port to connection to and the database name where applicable. <div>Lets gather some requirements here and we can then add some task for this.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 25 October 2013 14:33, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>the new Apache CouchDB store works fine:</div><div>* locally (1.4.0)</div><div>* Cloudant's DBaaS (based on: not exactly sure)</div>
<div><br></div><div><br></div><div>The local store was (obviously) not protected, but the cloudant offerings is protected.</div>
<div><br></div><div>I modified the testcase like:</div><div><br></div><div><div>... datastore = new CouchDBDataStore("<a href="https://matzew:PASSWORD@matzew.cloudant.com" target="_blank">https://matzew:PASSWORD@matzew.cloudant.com</a>", "simplepush-test");</div>
</div><div><br></div><div><br></div><div>sure that works, but I was wondering if we might (at a later time) wanna offer some 'properties' for user/password ?</div><div><br></div><div>Not saying it is an _urgent_ need - just a thought.</div>
<div><br></div><div><br></div><div>Anyways, I am happy w/ the Apache CouchDB support! :)</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>-M <br></div><div><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></font></span></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>