Add API Interface about netstoragekit-java HOT 3 OPEN

I'm still debating this one. I'm not a fan of an interface that will only ever have one implementation. I think a better mechanism is to provide a local loopback http service that simulates request and responses so the unit test is more comprehensive. (eg: offer a light weight http server that listens on an random port on localhost such as localhost:9999.) This server would simulates netstorage request/responses and auth checks. This could be helpful for this libraries own unit tests. Let me muse on this a bit.

from netstoragekit-java.

It's just good design to use interfaces, regardless of how many
implementations there are.
On Wed, Jun 15, 2016 at 10:14 AM Colin Bendell [email protected]
wrote:

I'm still debating this one. I'm not a fan of an interface that will only
ever have one implementation. I think a better mechanism is to provide a
local loopback http service that simulates request and responses so the
unit test is more comprehensive. (eg: offer a light weight http server that
listens on an random port on localhost such as localhost:9999.) This server
would simulates netstorage request/responses and auth checks. This could be
helpful for this libraries own unit tests. Let me muse on this a bit.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#11 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAVP-5GoeNkWz0fQ3vFuS3Pr64wqhy4xks5qMAfngaJpZM4IJ2Wj
.

from netstoragekit-java.

https://dzone.com/articles/to-interface-or-not-to-interface
On Wed, Jun 15, 2016 at 11:31 AM James Carman [email protected]
wrote:

It's just good design to use interfaces, regardless of how many
implementations there are.
On Wed, Jun 15, 2016 at 10:14 AM Colin Bendell [email protected]
wrote:

I'm still debating this one. I'm not a fan of an interface that will only
ever have one implementation. I think a better mechanism is to provide a
local loopback http service that simulates request and responses so the
unit test is more comprehensive. (eg: offer a light weight http server that
listens on an random port on localhost such as localhost:9999.) This server
would simulates netstorage request/responses and auth checks. This could be
helpful for this libraries own unit tests. Let me muse on this a bit.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#11 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAVP-5GoeNkWz0fQ3vFuS3Pr64wqhy4xks5qMAfngaJpZM4IJ2Wj
.

from netstoragekit-java.