old blog,

Introducing collective.trajectory : URL Routing, in Plone!!

Izhar Firdaus Izhar Firdaus Follow Support Sep 26, 2011 · 1 min read
Introducing collective.trajectory : URL Routing, in Plone!!
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.
When I was working with Martijn Faassen, I was introduced to traject, which is a library written by Martijn for URL routing. It is available to be used in Grok using megrok.traject, also by Martijn.

From that experience, I had the idea of integrating traject with Plone content type, so that we can have neat things like:
  • multiple instance of SQL application, in a single site, where each instance have different database url.
  • Use plone as the frontend proxy to other applications, where items from that application can be accessed through plone.
  • Those above are my primary motivation, but who knows what else this thing might open possibility to

I'm also hoping by having URL routing we make it easier for non-zope programmers to start developing stuff on Plone, as thats the common mechanism used in other Python web frameworks, and ZODB and graph traversal is something unfamiliar.

I've uploaded the code into collective. Only tested it roughly, but it works here on my Plone 4.1 buildout.


Have fun hacking :D
Written by Izhar Firdaus Follow Support
I'm a system architect, data engineer and developer advocate with passion in Free / Open Source software, entrepreneurship, community building, education and martial art. I take enjoyment in bridging and bringing together different FOSS technologies to help businesses and organizations utilize IT infrastructure to aid and optimize their business and organizational process.

Tracking email conversation in OpenERP Issue tracker.

So in Inigo we're trying to see whether we can use OpenERP for our support system. However, the email integration sucks, to the point...

In old blog, Sep 25, 2011

« Previous Post

Simple websocket push service using Tornado

WebSocket server side documentation/guides around tend to be very node.js oriented. However, I don't fancy rewriting stuff I already ...

In old blog, Oct 02, 2011

Next Post »