Use Advanced Search to search the entire archive.
[jsr363-experts] Re: Rename *Service as *Provider
- From: Leonardo Lima <
>
- To: "
" <
>
- Subject: [jsr363-experts] Re: Rename *Service as *Provider
- Date: Tue, 16 Dec 2014 07:57:36 -0200
I agree with this interpretation of words. The Provider provides a way to
get Service classes. The Provider does no work, it's only a gateway to a
Service, which does the work.
We just need a Jira issue to handle it, if there isn't one already.There we
can vote, too :)
Regards,
Leonardo.
On Sun, Dec 14, 2014 at 2:02 AM, Martin Desruisseaux <
>
wrote:
>
>
Le 13/12/14 23:19, Werner Keil a écrit :
>
>
With the new MicroService frency (also a concept strongly driven by
>
Fowler who inspired many of the underlying principles of the API like
>
Quantity;-) going across the entire industry right now, I think Service is
>
at least as appropriate or better.
>
>
I'm not sure that "Service" and "Provider" are the same thing.
>
>
- To me a service is like a "Web Service": I send a request to the
>
service, it performs some work, I get an answer, then I send a new
>
request
>
based on user action or previous request results, and so on. The Fowler's
>
description of "Micro Service" seems to be similar.
>
- To me a provider is a "on shut" action, like a connection to a
>
database: I get a "connection" (in our case, just a reference to a Java
>
object) to a service. Then, I can forget about the provider.
>
>
Indeed, "SPI" in the package name stands for "Service Provider Interface":
>
both "Service" and "Provider" are in the name. *Providers* provide
>
*services*. In JSR-363, I think that UnitFormat can be seen as a kind of
>
service. Consequently UnitFormatProvider would be the interface that give
>
me UnitFormat services.
>
>
Martin
>
>