Hello Chan, Sure.
How is the 21st? (after 1.00pm) Thank You, Sameera On Mon, Aug 19, 2013 at 2:02 PM, Chan <[email protected]> wrote: > Hi Nuwan, > +1 for the idea. How about we fix a review date and finalize the routing > aspect of Jaggery apps. Then we can have a unified router module ('Call it > Goose or whatever'). @SameeraM Shall we have the review this week if > possible? > > Express is highly influenced by [1] > Sinatra<http://www.sinatrarb.com/intro.html>- please refer Sinatra as well > since it's the backbone of most of the > routing modules built by other devs. > > Note:- I named the module goose since it refers to what inspired me to > write it. > > [1] - http://www.sinatrarb.com/intro.html > > Thanks. > > > On Mon, Aug 19, 2013 at 12:11 PM, Nuwan Bandara <[email protected]> wrote: > >> Hi Chan, >> >> The use of URIMatcher object in certain places of ES is by design. We are >> doing that to identify the URLPattern. its nothing related to HTTP Verb/url >> pattern based routing. >> >> We have written a simple router [1] to implement the REST API for ES [2]. >> But I do agree with you. It better to have a common routing module. which >> necessarily doesn't have to be a jaggery core module. >> >> Lets do a review of Goose library, we also have to look at other routing >> libraries, like which comes in expressjs etc. Can you co-ordinate with >> SameeraM and get this going. >> >> [1] >> https://github.com/wso2/enterprise-store/blob/master/modules/apps/publisher/modules/router.js >> [2] >> https://github.com/wso2/enterprise-store/blob/master/modules/apps/publisher/apis/v1/asset_api_router.jag >> [3] http://expressjs.com/api.html#app.routes >> >> Regards, >> /Nuwan >> >> >> On Sun, Aug 18, 2013 at 9:51 PM, Chan <[email protected]> wrote: >> >>> Hi all, >>> After going through the code base of Enterprise Store and Publisher I >>> have seen a lot of URIMatcher usages. We have written a module call goose >>> [1] on top of the URIMatcher that handles the URIMatcher transparently. >>> >>> Shall we setup a time and review it and adopt it to usage. Otherwise our >>> routing would be scattered and it won't look unified in different products. >>> Thanks. >>> >>> [1] - https://github.com/dulichan/goose.js >>> >>> -- >>> Chan (Dulitha Wijewantha) >>> Software Engineer - Mobile Development >>> WSO2Mobile >>> Lean.Enterprise.Mobileware >>> * ~Email [email protected]* >>> * ~Mobile +94712112165* >>> * ~Website dulithawijewantha.com >>> * >>> * ~Blog blog.dulithawijewantha.com<http://dulichan.github.io/chan/> >>> * >>> * ~Twitter @dulitharw <https://twitter.com/dulitharw>* >>> >> >> >> >> -- >> *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/> >> > > > > -- > Chan (Dulitha Wijewantha) > Software Engineer - Mobile Development > WSO2Mobile > Lean.Enterprise.Mobileware > * ~Email [email protected]* > * ~Mobile +94712112165* > * ~Website dulithawijewantha.com > * > * ~Blog blog.dulithawijewantha.com<http://dulichan.github.io/chan/> > * > * ~Twitter @dulitharw <https://twitter.com/dulitharw>* >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
