Hi All,
Moving on with Deployment Automation, we are evaluating a tool for
deploying cross platform setup in order to integrate with 3rd party
products with deployment framework.
Main concerns are
1. Testing actoss multiple environments (OS, JVM, DBs etc).
2. Limitness of resources to
Hi Harshan,
Thanks for the feedback. The list of IDs of the records to be retrieved can
be too long. So setting a list of ids as a query param is not convenient.
Even for the Search, we have to pass a query, which can be too long. Thats
why the post method is used for Search.
Thanks,
On Tue,
Hi Gimantha,
Could you please explain the use-case for the API #6? IMO there should not
be any operation to fetch a list of records by ids. Instead there could be
an API which sends a list of records as the response for a query.
For the API #14 you can still use GET method with query strings. I
Hi all,
I have completed basic repo separation discussed above along with commit
history of the code base.(https://github.com/ayshsandu/carbon-store). I
still need to include some necessary resource directories to this repo for
it to be fully functional.
There are 3 folders listed under
Hi,
Goood point!. Initially the search was implemented such a way that it
returns a list of ids of records that match the query. Now the search
method is changed, so it returns the records. So +1 for removing the API
#6.
@Sinduja, @Harshan
Thanks for the reference links and for the feedback.
Hi Gimantha,
You haven't really replied to Sinthuja's points there. We have to decide if
we are going ahead with Sinthuja's suggestions, or not. Lets first educate
ourselves on the best practices of RESTful API design a bit, Googling helps
[1]. For example, I'm also not sure if should be
