On Sun, Sep 29, 2013 at 8:38 PM, Srinath Perera <[email protected]> wrote:
> Mohan, our wizard assumes lot and it does not direct me to exactly what I > need to do next. For example, when I go to wizard, to add a query I need a > stream, before that I need a builder .. but nothing tells me I should have > created a builder first. > I agree we have to fix this in the next release. > > >> I'm -1 for the idea of in-line formatters/builders, this is because it >> will enable users to create same formatters multiple times and that will >> reduce the performance at the execution, & it will also make the config >> language and the whole stream flow much complex and unmaintainable. >> E.g what happens it i defines an in-line formatter to Foo Stream, if a >> another plan outputs Foo will it be also using this?? & etc >> >>> >>> Suho, if we ask users to define the stream first (via stream UI .. or > within a wizard that embed stream UIs), and then ask them to define the > mapping (builder or formatter) separately, I think then there is no > problem. Even if user end up defining the formatter twice, I think there > will be no real overhead. Did I miss something? Note currently we define > the stream as side effect of defining a builder. > > +1 for this, this is much clear, User can define execution plans and streams, and streams can have one or many builders/formatters. In this way Execution plans and streams will become the top level elements of CEP. Which is the correct thing. I think we can do these changes in the next release. WDYT? Regards Suho --Srinath > > > > -- *S. Suhothayan * Associate Technical Lead, *WSO2 Inc. *http://wso2.com * <http://wso2.com/>* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ twitter: http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan* * *
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
