Timeline for Should timeout be a public static property or a parameter to every function?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 7, 2013 at 3:23 | comment | added | Wyatt Barnett | @Alain -- you could call it ExecutePut() and the semantics work. | |
| Dec 7, 2013 at 3:21 | comment | added | Wyatt Barnett | @svick -- I'm not so sure. Or at least this developer rather enjoys fluent interfaces. | |
| Dec 6, 2013 at 21:03 | comment | added | Alain |
+1 This is a really neat idea. Unfortunately, my ClientAPI is a static class of extension methods (it's non-instantiable itself) so this syntax could never work. They'd have to do something like myMetaData.WithTimeout(30).Put(), which seems awkward since it's the Put method that is to be modified with a timeout, not the MetaData object.
|
|
| Dec 6, 2013 at 21:02 | comment | added | svick | I think this way is less convenient for the user of the library, but more convenient for its developer. But when developing a library, you should focus more on users' needs, I think. | |
| Dec 6, 2013 at 20:57 | history | edited | Wyatt Barnett | CC BY-SA 3.0 |
added 44 characters in body
|
| Dec 6, 2013 at 20:42 | history | answered | Wyatt Barnett | CC BY-SA 3.0 |