Comments on: Gigaspace API design – the GigaSpace write method http://martinaharris.com/2010/01/gigaspace-api-design-the-gigaspace-write-method/ Next time you look it might be gone Tue, 13 Jul 2010 22:32:05 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Martin Harris http://martinaharris.com/2010/01/gigaspace-api-design-the-gigaspace-write-method/#comment-18 Martin Harris Tue, 12 Jan 2010 21:21:45 +0000 http://martinaharris.com/?p=609#comment-18 Paul. You probably know this and it does not justify the test case thing but....its fairly easy to put together unit test cases that bring up GS in the test. I use this technique to build my own services that read and write from GS. Paul. You probably know this and it does not justify the test case thing but….its fairly easy to put together unit test cases that bring up GS in the test. I use this technique to build my own services that read and write from GS.

]]> By: Martin Harris http://martinaharris.com/2010/01/gigaspace-api-design-the-gigaspace-write-method/#comment-17 Martin Harris Tue, 12 Jan 2010 21:18:31 +0000 http://martinaharris.com/?p=609#comment-17 This makes a lot of sense. The sooner you can find time to re-factor them the better. I believe it will help with your market penetration if you can sort out this and improve the documentation. I for one would happily put up with some deprecation as long as its clear what is replacing the deprecation. This makes a lot of sense. The sooner you can find time to re-factor them the better. I believe it will help with your market penetration if you can sort out this and improve the documentation.

I for one would happily put up with some deprecation as long as its clear what is replacing the deprecation.

]]> By: Uri Cohen http://martinaharris.com/2010/01/gigaspace-api-design-the-gigaspace-write-method/#comment-16 Uri Cohen Mon, 11 Jan 2010 14:21:51 +0000 http://martinaharris.com/?p=609#comment-16 Hi Martin Thanks for your valuable feedback. I think you make a valid point. As a first step, we will make sure to improve the JavaDocs to better explain the meaning of each argument. And now to the detailed explanation: the OpenSpaces API is about 3 years old, and was originally modeled after our older JavaSpaces API. When we created the OpenSpaces API, we wanted to provide the smoothest migration path for our existing customers, and therefore wanted to keep the amount of changes minimal. Naturally, this came in some cases at the expense of creating a more modern and easier to use API. We have considered to change this API in recent releases, but eventually decided not to do so because we didn't want to further overload the existing API, such as the GigaSpace interface for example. However, we will at some point in the future have to deprecate older APIs, and we will definitely take your input into consideration in our upcoming releases. Note that this is not the case for our newer APIs, such as the administration and monitoring API, which makes use of method chaining, TimeUnit and other more modern patterns: http://www.gigaspaces.com/wiki/display/XAP7/Administration+and+Monitoring+API Uri (Product Manager at GigaSpaces) Hi Martin

Thanks for your valuable feedback. I think you make a valid point.
As a first step, we will make sure to improve the JavaDocs to better explain the meaning of each argument.

And now to the detailed explanation: the OpenSpaces API is about 3 years old, and was originally modeled after our older JavaSpaces API. When we created the OpenSpaces API, we wanted to provide the smoothest migration path for our existing customers, and therefore wanted to keep the amount of changes minimal. Naturally, this came in some cases at the expense of creating a more modern and easier to use API.

We have considered to change this API in recent releases, but eventually decided not to do so because we didn’t want to further overload the existing API, such as the GigaSpace interface for example. However, we will at some point in the future have to deprecate older APIs, and we will definitely take your input into consideration in our upcoming releases.

Note that this is not the case for our newer APIs, such as the administration and monitoring API, which makes use of method chaining, TimeUnit and other more modern patterns:
http://www.gigaspaces.com/wiki/display/XAP7/Administration+and+Monitoring+API

Uri (Product Manager at GigaSpaces)

]]> By: Paul Oliver http://martinaharris.com/2010/01/gigaspace-api-design-the-gigaspace-write-method/#comment-15 Paul Oliver Mon, 11 Jan 2010 08:38:42 +0000 http://martinaharris.com/?p=609#comment-15 Ditto that. I've spent so long struggling with the GigaSpaces documentation I've recommended to our company that we try Terracotta. The documentation is woeful. Not only that, but separation of concerns is never clear. My other pet hate is that whenever you contact support their standard response is "provide a test case". I would if you had supplied proper documentation to allow me to do this !! There is also an arrogance about the support that insinuates that you are stupid for asking the question. IMHO no matter how good the product is, it will never be more than a niche product for those obviously brighter and cleverer than me who are able to figure out how to use it. Ditto that. I’ve spent so long struggling with the GigaSpaces documentation I’ve recommended to our company that we try Terracotta. The documentation is woeful. Not only that, but separation of concerns is never clear.

My other pet hate is that whenever you contact support their standard response is “provide a test case”. I would if you had supplied proper documentation to allow me to do this !! There is also an arrogance about the support that insinuates that you are stupid for asking the question.

IMHO no matter how good the product is, it will never be more than a niche product for those obviously brighter and cleverer than me who are able to figure out how to use it.

]]>