Participants : UES Team, Mobile Team, APIM Team
1. As of now the mobile store is a folk of generic store
- It doesn't follow the same mvc structure
- only uses the existing common store modules to get the data pieces
2. Mobile team have developed a new MVC framework, which has some
similarities to caramel
3. Have developed the publisher and store with that framework
4. Discussed the framework and issues/limitations
*Action items*
1. We cannot have two ways of doing the same thing
2. We have identified the improvements needed to go into generic store
3. Have identified the limitations of the new mvc framework
4. We will be improving caramel with new suggestions
5. Mobile team will use the *Common Store, study it and build mobile
store with that with required improvements*
- This is not much of an effort because all the pieces are there
right now in mobile store current implementation. Its matter of
merging to
the generic store (Manu/Ruchira will aid from Store side)
6. Mobile team will take basic Caramel sample and put the publisher work
into that
7. Mobile team and UES/Store team will get to gather and improve the mvc
framework
8. Caramel can adopt front controller pattern as an option
9. Caramel should use (improve) the routing library mobile team have
developed
Over all we had a very productive meeting mobile team had done quite a lot
of JS development on Jaggery which is commendable Lets get the
improvements merged, and build one MVC framework for internal use
Mobile team/APIM team, please add if I have missed any
Regards,
/Nuwan
--
*Thanks & Regards,
Nuwan Bandara
Technical Lead; **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
