You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Udara Liyanage <ud...@wso2.com> on 2014/12/04 18:56:35 UTC
Shall we rename stratosmetadataservice web app
Hi All,
Similar to we rename Stratos => "api', shall we rename stratomedataservice
=> metaapi/metadataapi
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
Re: Shall we rename stratosmetadataservice web app
Posted by Udara Liyanage <ud...@wso2.com>.
On Fri, Dec 5, 2014 at 10:33 AM, Gayan Gunarathne <ga...@wso2.com> wrote:
>
> IMO if we use metaapi/metadataapi , it will be too long and also don't
> see any usage of maintain the two levels in the URL.
>
> Can't we use only metadataapi or metadataservice?
>
I meant metaapi or metadataapi, not metaapi/metadataapi. Sorry for my
wording.
>
>
> On Fri, Dec 5, 2014 at 7:52 AM, Nirmal Fernando <ni...@gmail.com>
> wrote:
>
>> Why not meta-data-service?
>>
>> On Fri, Dec 5, 2014 at 6:54 AM, Dakshika Jayathilaka <da...@wso2.com>
>> wrote:
>>
>>> +1
>>>
>>> *Dakshika Jayathilaka*
>>> Software Engineer
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>> 0771100911
>>>
>>> On Thu, Dec 4, 2014 at 11:26 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Similar to we rename Stratos => "api', shall we rename
>>>> stratomedataservice => metaapi/metadataapi
>>>> --
>>>>
>>>> Udara Liyanage
>>>> Software Engineer
>>>> WSO2, Inc.: http://wso2.com
>>>> lean. enterprise. middleware
>>>>
>>>> web: http://udaraliyanage.wordpress.com
>>>> phone: +94 71 443 6897
>>>>
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
>
> Gayan Gunarathne
> Technical Lead
> WSO2 Inc. (http://wso2.com)
> email : gayang@wso2.com | mobile : +94 766819985
>
>
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
Re: Shall we rename stratosmetadataservice web app
Posted by Imesh Gunaratne <im...@apache.org>.
+1 A good suggestion Mari!
On Sat, Dec 6, 2014 at 9:24 PM, Chamila De Alwis <ch...@wso2.com> wrote:
>
> On Sat, Dec 6, 2014 at 2:29 AM, Mariangela Hills <ma...@wso2.com>
> wrote:
>
>> /metadata/api
>
>
> +1
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: Shall we rename stratosmetadataservice web app
Posted by Chamila De Alwis <ch...@wso2.com>.
On Sat, Dec 6, 2014 at 2:29 AM, Mariangela Hills <ma...@wso2.com>
wrote:
> /metadata/api
+1
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
Re: Shall we rename stratosmetadataservice web app
Posted by Mariangela Hills <ma...@wso2.com>.
As metadata is one word [1], how about using the following:
/metadata/api
[1] http://en.wikipedia.org/wiki/Metadata
Regards,
Mariangela
*--*
Mariangela Hills
Senior Technical Writer
*WSO2, Inc.*lean.enterprise.middleware.
w: http://wso2.com
<http://wso2.com/events/>
On Fri, Dec 5, 2014 at 6:38 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Shall we use /meta-data/api
>
> On Fri, Dec 5, 2014 at 11:14 AM, Udara Liyanage <ud...@wso2.com> wrote:
>
>> Hi,
>>
>> Stratos REST API is used by clients (CLI,UI and curl) to manage stratos
>> system. However metadata API is supposed to used by cartridge agents to
>> publish and fetch metadata across application instances. Thus we have two
>> contexts.
>>
>>
>> On Fri, Dec 5, 2014 at 10:57 AM, Shiroshica Kulatilake <sh...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, Dec 5, 2014 at 10:52 AM, Gayan Gunarathne <ga...@wso2.com>
>>> wrote:
>>>
>>>> Meta data service is developed as a separate component.It can work as a
>>>> independent component and main idea of this to deploy the service without
>>>> Stratos.So it is not bundle in the common root.
>>>>
>>>
>>>
>>> OK - but when it is bundled with Stratos it becomes part of stratos
>>> right - not from an implementation aspect but more of a logical aspect -
>>> hence the question
>>>
>>> Scenario: User A is using Stratos via the REST APIs and this user needs
>>> to have two completely different contexts to get the work done from a
>>> single entity (black box Stratos)
>>>
>>>
>>>
>>>
>>>>
>>>>
>>>>
>>>> On Fri, Dec 5, 2014 at 10:39 AM, Shiroshica Kulatilake <sh...@wso2.com>
>>>> wrote:
>>>>
>>>>> I have a bit of a different question
>>>>>
>>>>> Since both of these are for stratos should we have a common root ?
>>>>>
>>>>> On Fri, Dec 5, 2014 at 10:33 AM, Gayan Gunarathne <ga...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> IMO if we use metaapi/metadataapi , it will be too long and also
>>>>>> don't see any usage of maintain the two levels in the URL.
>>>>>>
>>>>>> Can't we use only metadataapi or metadataservice?
>>>>>>
>>>>>>
>>>>>> On Fri, Dec 5, 2014 at 7:52 AM, Nirmal Fernando <
>>>>>> nirmal070125@gmail.com> wrote:
>>>>>>
>>>>>>> Why not meta-data-service?
>>>>>>>
>>>>>>> On Fri, Dec 5, 2014 at 6:54 AM, Dakshika Jayathilaka <
>>>>>>> dakshika@wso2.com> wrote:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> *Dakshika Jayathilaka*
>>>>>>>> Software Engineer
>>>>>>>> WSO2, Inc.
>>>>>>>> lean.enterprise.middleware
>>>>>>>> 0771100911
>>>>>>>>
>>>>>>>> On Thu, Dec 4, 2014 at 11:26 PM, Udara Liyanage <ud...@wso2.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi All,
>>>>>>>>>
>>>>>>>>> Similar to we rename Stratos => "api', shall we rename
>>>>>>>>> stratomedataservice => metaapi/metadataapi
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> Udara Liyanage
>>>>>>>>> Software Engineer
>>>>>>>>> WSO2, Inc.: http://wso2.com
>>>>>>>>> lean. enterprise. middleware
>>>>>>>>>
>>>>>>>>> web: http://udaraliyanage.wordpress.com
>>>>>>>>> phone: +94 71 443 6897
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Nirmal
>>>>>>>
>>>>>>> Nirmal Fernando.
>>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>>
>>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Gayan Gunarathne
>>>>>> Technical Lead
>>>>>> WSO2 Inc. (http://wso2.com)
>>>>>> email : gayang@wso2.com | mobile : +94 766819985
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Shiroshica Kulatilake
>>>>>
>>>>> Architect,
>>>>> WSO2, Inc. http://wso2.com/
>>>>> Phone: +94 776523867
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Gayan Gunarathne
>>>> Technical Lead
>>>> WSO2 Inc. (http://wso2.com)
>>>> email : gayang@wso2.com | mobile : +94 766819985
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Shiroshica Kulatilake
>>>
>>> Architect,
>>> WSO2, Inc. http://wso2.com/
>>> Phone: +94 776523867
>>>
>>
>>
>>
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
Re: Shall we rename stratosmetadataservice web app
Posted by Imesh Gunaratne <im...@apache.org>.
Shall we use /meta-data/api
On Fri, Dec 5, 2014 at 11:14 AM, Udara Liyanage <ud...@wso2.com> wrote:
> Hi,
>
> Stratos REST API is used by clients (CLI,UI and curl) to manage stratos
> system. However metadata API is supposed to used by cartridge agents to
> publish and fetch metadata across application instances. Thus we have two
> contexts.
>
>
> On Fri, Dec 5, 2014 at 10:57 AM, Shiroshica Kulatilake <sh...@wso2.com>
> wrote:
>
>>
>>
>> On Fri, Dec 5, 2014 at 10:52 AM, Gayan Gunarathne <ga...@wso2.com>
>> wrote:
>>
>>> Meta data service is developed as a separate component.It can work as a
>>> independent component and main idea of this to deploy the service without
>>> Stratos.So it is not bundle in the common root.
>>>
>>
>>
>> OK - but when it is bundled with Stratos it becomes part of stratos right
>> - not from an implementation aspect but more of a logical aspect - hence
>> the question
>>
>> Scenario: User A is using Stratos via the REST APIs and this user needs
>> to have two completely different contexts to get the work done from a
>> single entity (black box Stratos)
>>
>>
>>
>>
>>>
>>>
>>>
>>> On Fri, Dec 5, 2014 at 10:39 AM, Shiroshica Kulatilake <sh...@wso2.com>
>>> wrote:
>>>
>>>> I have a bit of a different question
>>>>
>>>> Since both of these are for stratos should we have a common root ?
>>>>
>>>> On Fri, Dec 5, 2014 at 10:33 AM, Gayan Gunarathne <ga...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>> IMO if we use metaapi/metadataapi , it will be too long and also
>>>>> don't see any usage of maintain the two levels in the URL.
>>>>>
>>>>> Can't we use only metadataapi or metadataservice?
>>>>>
>>>>>
>>>>> On Fri, Dec 5, 2014 at 7:52 AM, Nirmal Fernando <
>>>>> nirmal070125@gmail.com> wrote:
>>>>>
>>>>>> Why not meta-data-service?
>>>>>>
>>>>>> On Fri, Dec 5, 2014 at 6:54 AM, Dakshika Jayathilaka <
>>>>>> dakshika@wso2.com> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> *Dakshika Jayathilaka*
>>>>>>> Software Engineer
>>>>>>> WSO2, Inc.
>>>>>>> lean.enterprise.middleware
>>>>>>> 0771100911
>>>>>>>
>>>>>>> On Thu, Dec 4, 2014 at 11:26 PM, Udara Liyanage <ud...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> Similar to we rename Stratos => "api', shall we rename
>>>>>>>> stratomedataservice => metaapi/metadataapi
>>>>>>>> --
>>>>>>>>
>>>>>>>> Udara Liyanage
>>>>>>>> Software Engineer
>>>>>>>> WSO2, Inc.: http://wso2.com
>>>>>>>> lean. enterprise. middleware
>>>>>>>>
>>>>>>>> web: http://udaraliyanage.wordpress.com
>>>>>>>> phone: +94 71 443 6897
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Nirmal
>>>>>>
>>>>>> Nirmal Fernando.
>>>>>> PPMC Member & Committer of Apache Stratos,
>>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>>
>>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Gayan Gunarathne
>>>>> Technical Lead
>>>>> WSO2 Inc. (http://wso2.com)
>>>>> email : gayang@wso2.com | mobile : +94 766819985
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Shiroshica Kulatilake
>>>>
>>>> Architect,
>>>> WSO2, Inc. http://wso2.com/
>>>> Phone: +94 776523867
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Gayan Gunarathne
>>> Technical Lead
>>> WSO2 Inc. (http://wso2.com)
>>> email : gayang@wso2.com | mobile : +94 766819985
>>>
>>>
>>
>>
>>
>> --
>> Shiroshica Kulatilake
>>
>> Architect,
>> WSO2, Inc. http://wso2.com/
>> Phone: +94 776523867
>>
>
>
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: Shall we rename stratosmetadataservice web app
Posted by Udara Liyanage <ud...@wso2.com>.
Hi,
Stratos REST API is used by clients (CLI,UI and curl) to manage stratos
system. However metadata API is supposed to used by cartridge agents to
publish and fetch metadata across application instances. Thus we have two
contexts.
On Fri, Dec 5, 2014 at 10:57 AM, Shiroshica Kulatilake <sh...@wso2.com>
wrote:
>
>
> On Fri, Dec 5, 2014 at 10:52 AM, Gayan Gunarathne <ga...@wso2.com> wrote:
>
>> Meta data service is developed as a separate component.It can work as a
>> independent component and main idea of this to deploy the service without
>> Stratos.So it is not bundle in the common root.
>>
>
>
> OK - but when it is bundled with Stratos it becomes part of stratos right
> - not from an implementation aspect but more of a logical aspect - hence
> the question
>
> Scenario: User A is using Stratos via the REST APIs and this user needs to
> have two completely different contexts to get the work done from a single
> entity (black box Stratos)
>
>
>
>
>>
>>
>>
>> On Fri, Dec 5, 2014 at 10:39 AM, Shiroshica Kulatilake <sh...@wso2.com>
>> wrote:
>>
>>> I have a bit of a different question
>>>
>>> Since both of these are for stratos should we have a common root ?
>>>
>>> On Fri, Dec 5, 2014 at 10:33 AM, Gayan Gunarathne <ga...@wso2.com>
>>> wrote:
>>>
>>>>
>>>> IMO if we use metaapi/metadataapi , it will be too long and also don't
>>>> see any usage of maintain the two levels in the URL.
>>>>
>>>> Can't we use only metadataapi or metadataservice?
>>>>
>>>>
>>>> On Fri, Dec 5, 2014 at 7:52 AM, Nirmal Fernando <nirmal070125@gmail.com
>>>> > wrote:
>>>>
>>>>> Why not meta-data-service?
>>>>>
>>>>> On Fri, Dec 5, 2014 at 6:54 AM, Dakshika Jayathilaka <
>>>>> dakshika@wso2.com> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> *Dakshika Jayathilaka*
>>>>>> Software Engineer
>>>>>> WSO2, Inc.
>>>>>> lean.enterprise.middleware
>>>>>> 0771100911
>>>>>>
>>>>>> On Thu, Dec 4, 2014 at 11:26 PM, Udara Liyanage <ud...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> Similar to we rename Stratos => "api', shall we rename
>>>>>>> stratomedataservice => metaapi/metadataapi
>>>>>>> --
>>>>>>>
>>>>>>> Udara Liyanage
>>>>>>> Software Engineer
>>>>>>> WSO2, Inc.: http://wso2.com
>>>>>>> lean. enterprise. middleware
>>>>>>>
>>>>>>> web: http://udaraliyanage.wordpress.com
>>>>>>> phone: +94 71 443 6897
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Gayan Gunarathne
>>>> Technical Lead
>>>> WSO2 Inc. (http://wso2.com)
>>>> email : gayang@wso2.com | mobile : +94 766819985
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Shiroshica Kulatilake
>>>
>>> Architect,
>>> WSO2, Inc. http://wso2.com/
>>> Phone: +94 776523867
>>>
>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead
>> WSO2 Inc. (http://wso2.com)
>> email : gayang@wso2.com | mobile : +94 766819985
>>
>>
>
>
>
> --
> Shiroshica Kulatilake
>
> Architect,
> WSO2, Inc. http://wso2.com/
> Phone: +94 776523867
>
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
Re: Shall we rename stratosmetadataservice web app
Posted by Shiroshica Kulatilake <sh...@wso2.com>.
On Fri, Dec 5, 2014 at 10:52 AM, Gayan Gunarathne <ga...@wso2.com> wrote:
> Meta data service is developed as a separate component.It can work as a
> independent component and main idea of this to deploy the service without
> Stratos.So it is not bundle in the common root.
>
OK - but when it is bundled with Stratos it becomes part of stratos right -
not from an implementation aspect but more of a logical aspect - hence the
question
Scenario: User A is using Stratos via the REST APIs and this user needs to
have two completely different contexts to get the work done from a single
entity (black box Stratos)
>
>
>
> On Fri, Dec 5, 2014 at 10:39 AM, Shiroshica Kulatilake <sh...@wso2.com>
> wrote:
>
>> I have a bit of a different question
>>
>> Since both of these are for stratos should we have a common root ?
>>
>> On Fri, Dec 5, 2014 at 10:33 AM, Gayan Gunarathne <ga...@wso2.com>
>> wrote:
>>
>>>
>>> IMO if we use metaapi/metadataapi , it will be too long and also don't
>>> see any usage of maintain the two levels in the URL.
>>>
>>> Can't we use only metadataapi or metadataservice?
>>>
>>>
>>> On Fri, Dec 5, 2014 at 7:52 AM, Nirmal Fernando <ni...@gmail.com>
>>> wrote:
>>>
>>>> Why not meta-data-service?
>>>>
>>>> On Fri, Dec 5, 2014 at 6:54 AM, Dakshika Jayathilaka <dakshika@wso2.com
>>>> > wrote:
>>>>
>>>>> +1
>>>>>
>>>>> *Dakshika Jayathilaka*
>>>>> Software Engineer
>>>>> WSO2, Inc.
>>>>> lean.enterprise.middleware
>>>>> 0771100911
>>>>>
>>>>> On Thu, Dec 4, 2014 at 11:26 PM, Udara Liyanage <ud...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Similar to we rename Stratos => "api', shall we rename
>>>>>> stratomedataservice => metaapi/metadataapi
>>>>>> --
>>>>>>
>>>>>> Udara Liyanage
>>>>>> Software Engineer
>>>>>> WSO2, Inc.: http://wso2.com
>>>>>> lean. enterprise. middleware
>>>>>>
>>>>>> web: http://udaraliyanage.wordpress.com
>>>>>> phone: +94 71 443 6897
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Gayan Gunarathne
>>> Technical Lead
>>> WSO2 Inc. (http://wso2.com)
>>> email : gayang@wso2.com | mobile : +94 766819985
>>>
>>>
>>
>>
>>
>> --
>> Shiroshica Kulatilake
>>
>> Architect,
>> WSO2, Inc. http://wso2.com/
>> Phone: +94 776523867
>>
>
>
>
> --
>
> Gayan Gunarathne
> Technical Lead
> WSO2 Inc. (http://wso2.com)
> email : gayang@wso2.com | mobile : +94 766819985
>
>
--
Shiroshica Kulatilake
Architect,
WSO2, Inc. http://wso2.com/
Phone: +94 776523867
Re: Shall we rename stratosmetadataservice web app
Posted by Gayan Gunarathne <ga...@wso2.com>.
Meta data service is developed as a separate component.It can work as a
independent component and main idea of this to deploy the service without
Stratos.So it is not bundle in the common root.
On Fri, Dec 5, 2014 at 10:39 AM, Shiroshica Kulatilake <sh...@wso2.com>
wrote:
> I have a bit of a different question
>
> Since both of these are for stratos should we have a common root ?
>
> On Fri, Dec 5, 2014 at 10:33 AM, Gayan Gunarathne <ga...@wso2.com> wrote:
>
>>
>> IMO if we use metaapi/metadataapi , it will be too long and also don't
>> see any usage of maintain the two levels in the URL.
>>
>> Can't we use only metadataapi or metadataservice?
>>
>>
>> On Fri, Dec 5, 2014 at 7:52 AM, Nirmal Fernando <ni...@gmail.com>
>> wrote:
>>
>>> Why not meta-data-service?
>>>
>>> On Fri, Dec 5, 2014 at 6:54 AM, Dakshika Jayathilaka <da...@wso2.com>
>>> wrote:
>>>
>>>> +1
>>>>
>>>> *Dakshika Jayathilaka*
>>>> Software Engineer
>>>> WSO2, Inc.
>>>> lean.enterprise.middleware
>>>> 0771100911
>>>>
>>>> On Thu, Dec 4, 2014 at 11:26 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> Similar to we rename Stratos => "api', shall we rename
>>>>> stratomedataservice => metaapi/metadataapi
>>>>> --
>>>>>
>>>>> Udara Liyanage
>>>>> Software Engineer
>>>>> WSO2, Inc.: http://wso2.com
>>>>> lean. enterprise. middleware
>>>>>
>>>>> web: http://udaraliyanage.wordpress.com
>>>>> phone: +94 71 443 6897
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead
>> WSO2 Inc. (http://wso2.com)
>> email : gayang@wso2.com | mobile : +94 766819985
>>
>>
>
>
>
> --
> Shiroshica Kulatilake
>
> Architect,
> WSO2, Inc. http://wso2.com/
> Phone: +94 776523867
>
--
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985
Re: Shall we rename stratosmetadataservice web app
Posted by Shiroshica Kulatilake <sh...@wso2.com>.
I have a bit of a different question
Since both of these are for stratos should we have a common root ?
On Fri, Dec 5, 2014 at 10:33 AM, Gayan Gunarathne <ga...@wso2.com> wrote:
>
> IMO if we use metaapi/metadataapi , it will be too long and also don't
> see any usage of maintain the two levels in the URL.
>
> Can't we use only metadataapi or metadataservice?
>
>
> On Fri, Dec 5, 2014 at 7:52 AM, Nirmal Fernando <ni...@gmail.com>
> wrote:
>
>> Why not meta-data-service?
>>
>> On Fri, Dec 5, 2014 at 6:54 AM, Dakshika Jayathilaka <da...@wso2.com>
>> wrote:
>>
>>> +1
>>>
>>> *Dakshika Jayathilaka*
>>> Software Engineer
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>> 0771100911
>>>
>>> On Thu, Dec 4, 2014 at 11:26 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Similar to we rename Stratos => "api', shall we rename
>>>> stratomedataservice => metaapi/metadataapi
>>>> --
>>>>
>>>> Udara Liyanage
>>>> Software Engineer
>>>> WSO2, Inc.: http://wso2.com
>>>> lean. enterprise. middleware
>>>>
>>>> web: http://udaraliyanage.wordpress.com
>>>> phone: +94 71 443 6897
>>>>
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
>
> Gayan Gunarathne
> Technical Lead
> WSO2 Inc. (http://wso2.com)
> email : gayang@wso2.com | mobile : +94 766819985
>
>
--
Shiroshica Kulatilake
Architect,
WSO2, Inc. http://wso2.com/
Phone: +94 776523867
Re: Shall we rename stratosmetadataservice web app
Posted by Gayan Gunarathne <ga...@wso2.com>.
IMO if we use metaapi/metadataapi , it will be too long and also don't see
any usage of maintain the two levels in the URL.
Can't we use only metadataapi or metadataservice?
On Fri, Dec 5, 2014 at 7:52 AM, Nirmal Fernando <ni...@gmail.com>
wrote:
> Why not meta-data-service?
>
> On Fri, Dec 5, 2014 at 6:54 AM, Dakshika Jayathilaka <da...@wso2.com>
> wrote:
>
>> +1
>>
>> *Dakshika Jayathilaka*
>> Software Engineer
>> WSO2, Inc.
>> lean.enterprise.middleware
>> 0771100911
>>
>> On Thu, Dec 4, 2014 at 11:26 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> Similar to we rename Stratos => "api', shall we rename
>>> stratomedataservice => metaapi/metadataapi
>>> --
>>>
>>> Udara Liyanage
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> web: http://udaraliyanage.wordpress.com
>>> phone: +94 71 443 6897
>>>
>>
>>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985
Re: Shall we rename stratosmetadataservice web app
Posted by Nirmal Fernando <ni...@gmail.com>.
Just realized that you are referring to the context not the web app name.
On Fri, Dec 5, 2014 at 7:52 AM, Nirmal Fernando <ni...@gmail.com>
wrote:
> Why not meta-data-service?
>
> On Fri, Dec 5, 2014 at 6:54 AM, Dakshika Jayathilaka <da...@wso2.com>
> wrote:
>
>> +1
>>
>> *Dakshika Jayathilaka*
>> Software Engineer
>> WSO2, Inc.
>> lean.enterprise.middleware
>> 0771100911
>>
>> On Thu, Dec 4, 2014 at 11:26 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> Similar to we rename Stratos => "api', shall we rename
>>> stratomedataservice => metaapi/metadataapi
>>> --
>>>
>>> Udara Liyanage
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> web: http://udaraliyanage.wordpress.com
>>> phone: +94 71 443 6897
>>>
>>
>>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Shall we rename stratosmetadataservice web app
Posted by Nirmal Fernando <ni...@gmail.com>.
Why not meta-data-service?
On Fri, Dec 5, 2014 at 6:54 AM, Dakshika Jayathilaka <da...@wso2.com>
wrote:
> +1
>
> *Dakshika Jayathilaka*
> Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Thu, Dec 4, 2014 at 11:26 PM, Udara Liyanage <ud...@wso2.com> wrote:
>
>> Hi All,
>>
>> Similar to we rename Stratos => "api', shall we rename
>> stratomedataservice => metaapi/metadataapi
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Shall we rename stratosmetadataservice web app
Posted by Dakshika Jayathilaka <da...@wso2.com>.
+1
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Thu, Dec 4, 2014 at 11:26 PM, Udara Liyanage <ud...@wso2.com> wrote:
> Hi All,
>
> Similar to we rename Stratos => "api', shall we rename
> stratomedataservice => metaapi/metadataapi
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>