Hi,<div>I agree the "localPipe" seems like a bit strange weird, and it's implementation will be very simple and "dumb" but there will be situation maybe where we want to stay on the Pipe API, rather than shortcut to the datamanager, even if this Pipe just do a local loop, not sure I'm clear on this point but it is the idea of consistency ... </div>
<div>Seb </div><div><br><br><div class="gmail_quote">On Fri, Oct 26, 2012 at 3:03 PM, Kris Borchers <span dir="ltr"><<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">We are on the same page for the most part. :) Not sure what you mean by a "local pipe" though. I think that is what DataManager does. As for the event driven model for connecting and syncing a pipe to a store, I am already working on that on the JS side. Check out SyncManager in <a href="https://github.com/aerogear/aerogear-js/tree/SyncManager" target="_blank">https://github.com/aerogear/aerogear-js/tree/SyncManager</a>. There is still a lot to do and I have more code locally but it's a start.<div>
<br><div><div class="im"><div>On Oct 26, 2012, at 7:56 AM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>> wrote:</div><br></div><blockquote type="cite"><div class="im">
Hi all ! <div>I was looking at the all different documentation pages and FAQ, and some questions and ideas araise : </div><div><br></div></div><div>1) A PipeManager can contains 'n' pipes, is there any plan to be able to chain pipes together (i.e : "localPipe -> restPipe") ? Even nicer, would it be possible to make conditional the pipe "route" (i.e ; "no connection then use the localPipe" etc …) </div>
</blockquote><div class="im"><blockquote type="cite">
<div><br></div><div>2) The dataStore concept is clear but are there any plans to create some sort of association (one-to-one, one-to-many, etc ...) between a pipe and a datastore instance ?</div></blockquote></div><blockquote type="cite">
<div class="im"><div><br></div><div>3) One idea should be that a pipe produce events ("entering pipe","exiting pipe", with some useful callback data) and then any other component should be able to register to the pipe's events, same could be implemented for the other components (datastore events , security events) ...</div>
<div><br></div><div>The main idea is how we will consolidate all this different components together (pipe and datamanager mainly) onces we will have to deal with data sync for example. </div><div><br></div><div>I'm just throwing some ideas after a brainstorming with myself ;-) but please share your comments on this ! </div>
<div><br></div><div>Best Regards,</div><div>Seb</div><div><br></div></div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></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>
<br></blockquote></div><br></div>