Sorry, let me be more clear:<div><br></div><div>I have a Resource let's say CustomerRestService which is a leaf and handles everything related to '/customer'</div><div>Then I want a CustomerAddressRestService Resource, which is also a leaf and should handle everything related to '/customer/<customerId>/address'.</div>
<div><br></div><div>So I need a leaf Resource (i.e. it actually intercepts GET/POST/PUT/DELETE requests to the root '/customer' URL)</div><div>with a child leaf Resource (which intercepts the GET/POST/PUT/DELETE requests to its root '/customer/<customerId>/address' URL).</div>
<div><br></div><div>Twisted does not really allow for nested leaf resources, but REST is all about nested URL schemes, e.g. </div><div><br></div><div>Customer -> Customer Address</div><div>Customer -> Customer Phone</div>
<div>Customer -> Customer Invoice -> Customer Payment</div><div><br></div><div>etc.</div><div><br></div><div>Taking CorePost out of the picture and just going back to raw twisted.web, how would you recommend that be done?</div>
<div><br></div><div>Jacek</div>