Service deprecation

[Scott Gray-2]

Hi all,

What do you think about adding the ability to deprecate services?  We  
could add an attribute to the service definition indicating that it  
has been deprecated and then log a warning whenever it is invoked.  
That would allow us to change the names of or remove services without  
breaking existing installations, we'd just move the old service to the  
bottom of the service definition file and then remove it after the  
next release.

I don't have a pressing need for this, it's just an idea I had after  
seeing some poorly named services around the place.

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

[Sumit Pandit-3]

+1,
This would be a good idea, Including this I would be good to have two  
attribute instead of one - One for indicating that it has been  
deprecated (as Scott's suggested) and second one tell the name of  
service/s that will replace the deprecated service.

--
Thanks And Regards
Sumit Pandit

On 24-Sep-09, at 8:19 AM, Scott Gray wrote:

> Hi all,
>
> What do you think about adding the ability to deprecate services?  
> We could add an attribute to the service definition indicating that  
> it has been deprecated and then log a warning whenever it is  
> invoked.  That would allow us to change the names of or remove  
> services without breaking existing installations, we'd just move the  
> old service to the bottom of the service definition file and then  
> remove it after the next release.
>
> I don't have a pressing need for this, it's just an idea I had after  
> seeing some poorly named services around the place.
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com

[Scott Gray-2]

A deprecation message would be a good idea, perhaps we could just have  
that as the single attribute, if the attribute has content then the  
service is deprecated.  Doing so would force a developer to include a  
message in order to deprecate a service.

Regards
Scott

On 24/09/2009, at 3:44 PM, Sumit Pandit wrote:

> +1,
> This would be a good idea, Including this I would be good to have  
> two attribute instead of one - One for indicating that it has been  
> deprecated (as Scott's suggested) and second one tell the name of  
> service/s that will replace the deprecated service.
>
> --
> Thanks And Regards
> Sumit Pandit
>
> On 24-Sep-09, at 8:19 AM, Scott Gray wrote:
>
>> Hi all,
>>
>> What do you think about adding the ability to deprecate services?  
>> We could add an attribute to the service definition indicating that  
>> it has been deprecated and then log a warning whenever it is  
>> invoked.  That would allow us to change the names of or remove  
>> services without breaking existing installations, we'd just move  
>> the old service to the bottom of the service definition file and  
>> then remove it after the next release.
>>
>> I don't have a pressing need for this, it's just an idea I had  
>> after seeing some poorly named services around the place.
>>
>> Regards
>> Scott
>>
>> HotWax Media
>> http://www.hotwaxmedia.com
>

[Jacques Le Roux]

+1, and maybe another field to comment

Jacques

From: "Sumit Pandit" <[hidden email]>

> +1,
> This would be a good idea, Including this I would be good to have two  
> attribute instead of one - One for indicating that it has been  
> deprecated (as Scott's suggested) and second one tell the name of  
> service/s that will replace the deprecated service.
>
> --
> Thanks And Regards
> Sumit Pandit
>
> On 24-Sep-09, at 8:19 AM, Scott Gray wrote:
>
>> Hi all,
>>
>> What do you think about adding the ability to deprecate services?  
>> We could add an attribute to the service definition indicating that  
>> it has been deprecated and then log a warning whenever it is  
>> invoked.  That would allow us to change the names of or remove  
>> services without breaking existing installations, we'd just move the  
>> old service to the bottom of the service definition file and then  
>> remove it after the next release.
>>
>> I don't have a pressing need for this, it's just an idea I had after  
>> seeing some poorly named services around the place.
>>
>> Regards
>> Scott
>>
>> HotWax Media
>> http://www.hotwaxmedia.com
>

[Mridul Pathak-2]

+1.  I think that a single attribute, something like deprecation-
message or deprecation-comment, should do the job.

--
Thanks,
Mridul Pathak

On 24-Sep-09, at 9:24 AM, Scott Gray wrote:

> A deprecation message would be a good idea, perhaps we could just  
> have that as the single attribute, if the attribute has content then  
> the service is deprecated.  Doing so would force a developer to  
> include a message in order to deprecate a service.
>
> Regards
> Scott
>
> On 24/09/2009, at 3:44 PM, Sumit Pandit wrote:
>
>> +1,
>> This would be a good idea, Including this I would be good to have  
>> two attribute instead of one - One for indicating that it has been  
>> deprecated (as Scott's suggested) and second one tell the name of  
>> service/s that will replace the deprecated service.
>>
>> --
>> Thanks And Regards
>> Sumit Pandit
>>
>> On 24-Sep-09, at 8:19 AM, Scott Gray wrote:
>>
>>> Hi all,
>>>
>>> What do you think about adding the ability to deprecate services?  
>>> We could add an attribute to the service definition indicating  
>>> that it has been deprecated and then log a warning whenever it is  
>>> invoked.  That would allow us to change the names of or remove  
>>> services without breaking existing installations, we'd just move  
>>> the old service to the bottom of the service definition file and  
>>> then remove it after the next release.
>>>
>>> I don't have a pressing need for this, it's just an idea I had  
>>> after seeing some poorly named services around the place.
>>>
>>> Regards
>>> Scott
>>>
>>> HotWax Media
>>> http://www.hotwaxmedia.com
>>
>