No subject

Fri Oct 28 10:01:47 EDT 2011

ld Resources of its own (no requests seem to get routed to them).<div><br><=
/div><div>This is not really a realistic scenario in a typical REST applica=
tion where nested REST services are common, e.g.</div>
<div><br></div><div>Customer REST service:</div><div><br></div><div><i>GET =
/services/customer</i></div><div><i>POST /services/customer</i></div><div><=
i>PUT /services/customer/&lt;customerId&gt;</i></div><div><i>DELETE /servic=
<div><br></div><div>Customer Address REST service:</div><div><br></div><div=
><div><i>GET /services/customer/&lt;customerId&gt;/address</i></div><div><i=
>POST /services/customer/&lt;customerId&gt;/address</i></div><div><i>PUT /s=
<div><i>DELETE /services/customer/&lt;customerId&gt;/address/&lt;addressId&=
gt;</i></div></div><div><br></div><div>and so on and so forth....</div><div=
><br></div><div>The only way I can support this in CorePost is to separate =
the concept of a Twisted.Web Resource from a standalone REST service for a =
particular entity.</div>
<div><br></div><div>So let&#39;s say I would have a root CorePost Resource =
hooked up to &#39;services&#39; and it would have a child collection of RES=
T service classes and manage routing the requests<br>to the appropriate one=
. Each of the REST services for an entity underneath that core Resource wou=
ld NOT be a twisted.web Resource but just a regular class.</div>
<div><br></div><div>Does this sound correct?</div><div>Or am I missing some=
 way of using twisted.web Resource objects that would allow me to accomplis=
h the same thing without moving away from Resource</div><div>as the ancesto=
r of all my REST service classes?</div>


More information about the Twisted-web mailing list