[RCBC-78] Need Alternative to Event Loop Created: 27/Aug/12 Updated: 28/Aug/12 |
|
| Status: | Open |
| Project: | Couchbase Ruby client library |
| Component/s: | library |
| Affects Version/s: | 1.0.0, 1.1.0, 1.2.0.z.beta |
| Fix Version/s: | 2.0.0 |
| Security Level: | Public |
| Type: | Improvement | Priority: | Major |
| Reporter: | Karen Zeller | Assignee: | Sergey Avseyev |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Production Management (DiptiP), and Customer Support team request that we provide an alternative to the event loop for asynchronous operations, which takes a function/callback as a parameter in the method signature and has an explicit return.
|
| Comments |
| Comment by Matt Ingenthron [ 28/Aug/12 ] |
|
In the future, it'd be good for Product Management(sic) to talk with product management: me. :)
This is not something planned in the short term. Moving to 2.0. |
[RCBC-75] Provide Consistent Order of Parameters Created: 24/Aug/12 Updated: 02/Jan/13 |
|
| Status: | Open |
| Project: | Couchbase Ruby client library |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.0 |
| Security Level: | Public |
| Type: | Improvement | Priority: | Major |
| Reporter: | Karen Zeller | Assignee: | Matt Ingenthron |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Provide consistent, predictable order for method parameters as other SDKS.
|
| Comments |
| Comment by Sergey Avseyev [ 24/Aug/12 ] |
| Could you extend your query please with examples? Where the API is inconsistent and unpredictable? |
| Comment by Karen Zeller [ 27/Aug/12 ] |
|
Here is the first example. This may require a fix on the Java side vs. the Ruby side:
http://www.couchbase.com/docs/couchbase-sdk-java-1.0/couchbase-sdk-java-set-add.html#table-couchbase-sdk_java_add Order is key, expiry, then value Should be one fairly consistent order across the SDKs. Will add others as either I or others (customer support) run across them. |
| Comment by Karen Zeller [ 27/Aug/12 ] |
| I have reassigned this to Matt so this can be looked at globally post 2.0, and hopefully approached across the SDKs. This is a repeated request I am getting from customer support. |