Bogdan,<div>For both it would make sense to use JSON I think. Moreso for couchbase which understands JSON natively.</div><div><br></div><div>For the key, just setting it as a TimeUUID I think would make a lot of sense. </div>
<div><br></div><div>-Brett</div><div><br></div><div><br></div><div><br></div><div><div class="gmail_quote">On Fri, Oct 26, 2012 at 5:02 PM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Hi Brett,</div><div><br></div><div>Indeed that's something interesting...and how to pack all fields into a single value? Json ? Also the key name should be time based....i guess we need to dynamically generate them.</div>
<div><br></div><div>Regards,</div><div>Bogdan</div><div><br></div><div><br></div><div><div style="font-size:75%;color:#575757">Sent from Samsung Mobile</div></div><div><div class="h5"> <br>Brett Nemeroff <<a href="mailto:brett@nemeroff.com" target="_blank">brett@nemeroff.com</a>> wrote:<br>
Bogdan,<div>Very excited to see NOSQL support. I know we discussed this before, but is there any possibility of native acc support for any NOSQL backend? </div><div><br></div><div>Thanks!</div><div>-Brett</div><div><br></div>
<div><br><br><div class="gmail_quote">On Fri, Oct 26, 2012 at 10:20 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
I would like to start a discussion about the next OpenSIPS major release - and in this discussion anyone is welcomed with options, ideas, critics and other. Your feedback is important to drive the project into a direction that reflects the user's needs!.<br>
<br>
So, I will here the starting points, for both release planing and release content.<br>
<br>
<br>
Content<br>
-------<br>
What was done:<br>
<a href="http://www.opensips.org/Main/Ver190#toc2" target="_blank">http://www.opensips.org/Main/<u></u>Ver190#toc2</a><br>
What is planned:<br>
<a href="http://www.opensips.org/Main/Ver190#toc9" target="_blank">http://www.opensips.org/Main/<u></u>Ver190#toc9</a><br>
Planned items have priorities (for being addressed); it is a must to have all items done for the next release, as we need to fit into a time frame. Whatever is not done, will be left for the next release (1.10)<br>
<br>
<br>
Planing<br>
-------<br>
Release candidate:<br>
second half of January 2012, depending on the progress with the items to be done.<br>
Testing phase:<br>
1 month allocated (it may be extended if critical problems show up)<br>
Stable release:<br>
second half of February (after the testing phase is done).<br>
<br>
<br>
Once again, your feedback on these matters is important to us.<br>
<br>
<br>
Best regards,<span><font color="#888888"><br>
<br>
-- <br>
Bogdan-Andrei Iancu<br>
OpenSIPS Founder and Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.<u></u>com</a><br>
<br>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-<u></u>bin/mailman/listinfo/users</a><br>
</font></span></blockquote></div><br></div>
</div></div></div></blockquote></div><br></div>