Hello Everyone,
*Description:*
The review looked at the use of the Jaggery-Pipe [3] ( a middleware
implementation like connect.js [1] ) and the simpleRouter plug-in [4] that
will be integrated into the Store and Publisher. These new components will
be used to handle routing and support for additional extension points in
the Store and Publisher.
*Participants*:
*Enterprise Store Team*: Ruchira, Praveena,Tanya, Nadeesha and Sameera
*Mobile Team:* Dulitha (Chan)
*Observations:*
- There is no need to allow users to define multiple routes to a single
handler in one line. This can be handled by defining each route in a
single line, in order to promote readability
- There is no need to allow users to override a plug-in used in the pipe
*Actions:*
- The underlying implementation of the simpleRouter needs to be changed
so that it creates a tree structure from each route. This will allow the
definition of multiple route levels;
- /store/asset/:type/:id
- /store/asset/api/:id
- The simpleRouter should operate in two modes: development and
production
- In the development mode the route tree should be constructed for
each request
- In the production mode the route tree should only be built once
- The variables in a route should be defined using : (colons) as opposed
to { (curly braces):
- Current: /store/asset/{type}
- New: /store/asset/:type
- This is the implementation used in other JavaScript routing
frameworks (e.g. Express [2] )
*References*
[1] Connect.js ,URL: http://www.senchalabs.org/connect/
[2] Express.js ,URL: http://expressjs.com/guide.html
[3] Jaggery-Pipe ,URL:https://github.com/splinter/jaggery-pipe
[4] simpleRouter ,URL:
https://github.com/splinter/jaggery-pipe/blob/master/plugins/simpleRouter.js
Thank You,
Sameera
--
Sameera Medagammaddegedara
Software Engineer
Contact:
Email: [email protected]
Mobile: + 94 077 255 3005
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
