there shouldn't be two unique ways to identify a issue. Issue ID itself should be a unique key (possible a String).
On Thu, Aug 22, 2013 at 6:17 AM, Nihanth Joseph <[email protected]> wrote: > Hi Ramith, > To process Issue details, are we going to pass issue id or unique key > (String) of issue? > if we are passing unique key then in-order to add/ get/ update/ delete > comments we have to do two DB calls, first call to get issue id for unique > key and second one is for real purpose (add/ delete/ edit/ delete comments) > which one is better way? > > > On Fri, Aug 16, 2013 at 10:25 AM, Ramith Jayasinghe <[email protected]>wrote: > >> Nope. >> I don't think we required versioned url as of now. >> >> >> >> On Fri, Aug 16, 2013 at 12:46 AM, Shameera Rathnayaka >> <[email protected]>wrote: >> >>> Hi Ramith, >>> >>> Is this REST url schema has versioning support? >>> >>> Thanks, >>> Shameera. >>> >>> >>> On Wed, Aug 14, 2013 at 6:42 PM, Ramith Jayasinghe <[email protected]>wrote: >>> >>>> Hi, >>>> This is what we propose as the URL scheme for issue tracking component >>>> we are writing. >>>> >>>> GET /issue/<id> -- Returns information about an issue. >>>> POST /issue/<id>/ -- modifies an existing issue. >>>> >>>> POST /issue/<id>/comment -- adds new comment to an issue >>>> POST /issue/<id>/comment/<id> -- modifies an existing comment >>>> >>>> DELETE /issue/<id>/comment/<id> -- deletes a existing comment >>>> >>>> >>>> GET /project -- returns a list of projects for the organization >>>> GET /project/<id> --- gets information about project >>>> >>>> >>>> POST /project/ -- adds a new project >>>> POST /project/<id> -- edits information of an exiting project >>>> >>>> GET /project/<id>/version -- list of versions of the project >>>> GET /project/<id>/issue -- list of issues of the project >>>> >>>> >>>> POST /project/<id>/issue/ -- add a new issue to an project. >>>> >>>> >>>> These are only the basic operations we might need (we will devise URL >>>> as we go along for other use cases). >>>> Note that above URLs don't have organization Id included. >>>> >>>> WDYT? >>>> >>>> >>>> >>>> regards >>>> Ramith >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Software Engineer - WSO2 Inc.* >>> *email: shameera AT wso2.com <[email protected]> , shameera AT >>> apache.org <[email protected]>* >>> *phone: +9471 922 1454* >>> * >>> * >>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>> *Twitter : *https://twitter.com/Shameera_R >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Ramith Jayasinghe >> Technical Lead >> WSO2 Inc., http://wso2.com >> lean.enterprise.middleware >> >> E: [email protected] >> P: +94 776715671 >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Nihanth Joseph > Senior Software Engineer > Mob: +94719187136 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- With regards, *Manu*ranga Perera.
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
