Hi All,
On Tue, May 21, 2013 at 9:04 PM, Chan <[email protected]> wrote: > Dear all, > > We held an architecture review meeting regarding the Mobile AppStore that > will be built on top of the WSO2 Store. Below are the issues we discussed - > > *Adding Support to Categories* > We need to add category level support to the store as per the use case of - > Business Applications -> Tools. The support for categories has to be > provided by the GReg. > @Senaka, how can we proceed with this, is there a GREG level implementation to support categories, or can it be just a feild in RXT definition ? > > *Adding hierarchical support for Assets* > For the store artifacts needs to have a notion of inheritance - Apps > include iOS, Android, BlackBerry. But GReg doesn't support inheritance for > artifacts. The conclusion brought forward was to use a meta data specifying > the os type and rendering custom pages for OS. > I dont this the correct message is conveyed here. RXT doesn't have a hierarchy by design, which is fine. what you will have to do is, add a feild called "type" in the Mobile App RXT definition and filter the menus etc by that field. > > *Publishing Component* > Also a publishing component has to be written as well for full life cycle > management of applications, notifications. The component also has to be > role based- Developer login, Curator login (for app reviewing), End user > login. > > *Rhino issue* > Inherent speed issue was also addressed. We are going to be using jaggery > for our API's considering the fact that API managers load tests have proven > the robustness of the underlying JavaScript engine. In the new javascript > engine (Nashhorn <https://blogs.oracle.com/nashorn/>) which will be > available in Java 8 will be be 4x time faster than Rhino. > I am against calling this an "issue" in Rhino. Rhino is one of the best libraries I have used with a well thought extensible architecture. Of-cause there is a performance nag when compared to pure Java or C/C++ but oppose to that benefits are massive. So even there are no improvment in JDK 8, I still prefer writing my code is jaggery rather than in java (of-cause I am bias :) ) > > *Routing conventions* > Current routing style will continue on abstracting routing and the logic. > The jaggery team has come up with an architecture to have the jaggery core > picking up routes from a folder. > +1, this is the next item in our jaggery roadmap, as soon as we complete UES work we are going to work on this. > > *Github* > The MDM project will migrate into a Public Github repo so that everyone > can view and contribute to the source. This decision was taken cause the > WSO2 Kernel versions and everything will be transferring to Github. > +1, I suggest you guys create a new organization called wso2mobile in GitHub and develop on that under Apache2 licence. Regards, /Nuwan > > *End User theming* > Theming of the generic store needs to be done as per what we discussed. > > I hope I didn't miss anything. > -- > Chan (Dulitha Wijewantha) > Software Engineer - Mobile Development > WSO2Mobile > Lean.Enterprise.Mobileware > * ~Email [email protected]* > * ~Mobile +94712112165* > * ~Website dulithawijewantha.com > * > * ~Blog blog.dulithawijewantha.com > * > * ~Twitter @dulitharw <https://twitter.com/dulitharw>* > -- *Thanks & Regards, Nuwan Bandara Technical Lead & Member, MC, Development Technologies WSO2 Inc. - lean . enterprise . middleware | http://wso2.com blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 9629 * <http://www.nuwanbando.com/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
