On Mon, Oct 6, 2014 at 7:51 AM, Udara Liyanage wrote:
> +1 for api/version
>
>
>
> Touched, not typed. Erroneous words are a feature, not a typo.
> On Oct 5, 2014 11:11 PM, "Akila Ravihansa Perera"
> wrote:
>
>> On Sun, Oct 5, 2014 at 10:22 PM, Nirmal Fernando
>> wrote:
>> > Exactly! That's how
+1 for api/version
Touched, not typed. Erroneous words are a feature, not a typo.
On Oct 5, 2014 11:11 PM, "Akila Ravihansa Perera"
wrote:
> On Sun, Oct 5, 2014 at 10:22 PM, Nirmal Fernando
> wrote:
> > Exactly! That's how most of the popular APIs are designed.
> >
> > On Sun, Oct 5, 2014 at
On Sun, Oct 5, 2014 at 10:22 PM, Nirmal Fernando wrote:
> Exactly! That's how most of the popular APIs are designed.
>
> On Sun, Oct 5, 2014 at 10:13 PM, Dakshika Jayathilaka
> wrote:
>>
>> Hi,
>>
>> i think d best approach would be having api and version number on context.
>>
>> api/v1
+1
>>
Exactly! That's how most of the popular APIs are designed.
On Sun, Oct 5, 2014 at 10:13 PM, Dakshika Jayathilaka
wrote:
> Hi,
>
> i think d best approach would be having api and version number on context.
>
> api/v1
>
> Regards,
>
> *Dakshika Jayathilaka*
> Software Engineer
> WSO2, Inc.
> lean.
Hi,
i think d best approach would be having api and version number on context.
api/v1
Regards,
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Sun, Oct 5, 2014 at 9:15 PM, Nirmal Fernando
wrote:
> Hi Devs,
>
> Currently the API root context is 'ad
Hi Devs,
Currently the API root context is 'admin'. Does that make any sense to have
'admin' instead of having 'api' ? What consequences it would bring if we
refactor the root context?
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer,
