Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I'm looking for a Java/Android implementation of promises that allow chaining and joining.
With chaining I mean chaining then calls so code looks like synchronous.
// Example:
getCity().then(getRestaurants).then(findBestMenu);
With joining I mean waiting for multiple promises to be fulfilled, or any of them fail.
// Example:
Promise p1 = getFlights();
Promise p2 = getHotels();
PromiseManager.when(p1,p2).then(planTrip).fail(stayAtHome);
I have found these solutions:
RxJava-Promises supports chaining via PromiseFunction and RepromiseFunction.
jdeferred supports joining via DeferredManager. EDIT: It also supports chaining via DonePipe.
EDIT2:
RxJava or RxAndroid are for reactive paradigm. A bit more complex but powerful.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
In a recent interview with Amazon I have been rejected because I could not tell the advantage and disadvantage of making model and Entity classes different and same.
I have always created Model and Entity class same.
Can anybody help me on that with an example? Interviewer said you are making strong binding of UI+DB if you are keeping it same.
It's true by making same class for Entity and Model you are tightly binding UI and DB, simple example of why should avoid is -> most of the time, we modify response like adding DTO, modifying format of date and so on. which could impact your database calls (DTO layer).you can read more here
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
In the Datastore v1Beta2 API version, DatastoreHelper was a public class, and we rely on member functions like getOptionsFromEnv(), getComputeEngineCredential(), makeFilter() and makeValue(). Looks like that class is now private in the v1 API. What's the equivalent class that will provide us access to those functions?
Most of those methods are still public in google-cloud-datastore library:
https://github.com/GoogleCloudPlatform/google-cloud-datastore/blob/master/java/datastore/src/main/java/com/google/datastore/v1/client/DatastoreHelper.java
getComputeEngineCredential() was removed, but you can use Application Default Credentials instead, which supports getting a credential from Compute Engine.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I'm trying to solve the following problem:
I have some expensive work to do which I then cache the result of
The work is keyed by a string
Many requests may arrive simultaneously for the same key
I'd like to avoid doing the work more than once per key
I'd like to add callbacks against the key which will be invoked when the work is completed; not all of these are known when the work is first submitted.
This feels like a problem which ought to have been solved already; does anybody know of a Java framework or library which covers it?
I can imagine a wrapper around guava's LoadingCache but I'm not aware of a library which does everything out of the box.
While LoadingCache#get is synchronous, it does get you 1-4 and there may be some mileage in using refresh which can return a ListenableFuture (although to get all the features you list it might become a fairly chunky wrapper?)
For Reference:
http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/cache/LoadingCache.html#refresh(K)
http://www.theotherian.com/2013/11/non-blocking-cache-with-guava-and-listenable-futures.html
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I want to match regular expressions very fast, low overhead. And I want to be able to choose between multiple expressions.
E.g.
AB* -> case A
XXX -> case B
etc
So I want to name all of which cases matched.
The problem is very similar to a lexical analyzer but the patterns are dynamic. That is, a user could change them at any time. So I don't have the luxuary of re-running Lex. Plus, I could have any number of different matchers.
I don't need any of the subpattern identification/capture stuff in Java or the overhead.
Just need to know which cases matched.
I could write software to do this efficiently...but it would almost be like re-writing lex.
Are there any tools that can do this?
Are there any more efficient regular expression libraries than the built in ones in java? Thread safe, etc.
thanks.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I am new to REST design patterns. I am trying to write an API with following design in mind.
GET http://www.example.com/customers/33245/orders/8769/lineitems/1
I am able to write basic REST services with Java (JAX-RS) using Jersey:
GET|PUT|DELETE http://www.example.com/customers/{id}
Any tutorial that explains how we should do such multi-node routing in Java would be really helpful.
Thanks,
Kush
You should probably go with something like this (this is a snippet from the resource class):
...
#GET
#Path("customers/{customer-id}/orders/{order-id}/lineitems/{lineitem-id}")
public Response get(#PathParam("customer-id") String customerId, #PathParam("order-id") String orderId, #PathParam("lineitem-id") String lineItemId) {
// fetch logic goes here...
}
...