Sam Goldstein wrote: > You're right that the routes on kiwi.drasticcode.com leave something > to be desired. I was mainly focused on getting a demo of the parser > working, and didn't put a lot of thought into the urls, or try to > follow any wiki best practices. I did try to avoid some of the > MediaWiki conventions, like putting colons in routes, or indicating > the action with a GET param. I've found these can be tricky to > duplicate in other frameworks like Rails, which doesn't easily support > those. > > I would like to find the time to address this (although Karl's right > that I would welcome contributions.) I'm considering that a routing > scheme like this might work: > > GET /wiki/a-page-name > GET /wiki/another/page > GET /edit/another/page > GET /upload/someFile.jpg > POST /wiki/another/page # update or create > > Are there any obvious problems with this approach I might want to consider? > > Thanks > Sam Goldstein
Looks fine to me. I am so used to the problem of "wikis in root folder" that I immediately noticed the flaw in your pattern, but I admit it's easy not to notice those problems when planning the urls. _______________________________________________ Wikitext-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitext-l
