reactive-programming

Given a synchronous observer, is there a way to do this: observable.SubscribeAsync(observer); And have all methods on the observer called asynchronously or is that something I have to handle when creating the observer? meilke You might want to look into ObserveOn and SubscribeOn ( more information and even more information ). If you need to call an async method when the stream spits out a new value, the most common solution you will find is to use SelectMany . The problem is that this doesn't wait for the method to finish, causing any tasks created by SelectMany to run in parallel. Here's what

I have a selectizeInput in my Shiny app. It is in multiple-select mode, so the user can specify more than one selection. However, the reactives that depend on the selectizeInput get fired every time a selection is added. Suppose that the user intends to select A , B and C . Currently, my app will do it expensive computations for the selections A , A, B and A, B, C , when only the last is required. The best way I can think to solve this is to delay the firing of the selectizeInput by a second or so to give the user a chance to enter all of the selections. Each new selection should set the timer

I am new to ReactiveX for Java and I've the following code block that make external http call but it is not async. We are using rxjava 1.2, and Java 1.8 private ResponseEntity<String> callExternalUrl(String url, String json, HttpMethod method) { RestTemplate restTemplate; HttpEntity request; request = new HttpEntity(jsonContent, httpHeaders); return restTemplate.exchange(url, httpMethod, request, String.class); } I've the following code block I found online but I couldn't totally understand it and how I can apply it to my code base. private RxClient<RxObservableInvoker> httpClient; public <T>

I have been using Rx for a while now for Events on my projects and dedicatedly for Socket programming and the good part is its doing well. Managing my code, performance advantage and much better to execute and interpret. Lately I have to modify my project's process flow where i need to dump all the incoming data (from socket operations) into queues ( using MSMQ implementation as decided for queueing ). As MSMQ provides async call for dequeing messages from the queue (but in an wierd pattern). I have been struggling to use Rx for this purpose now, but enable to do so. Question : Can some one

In Spring Data, we have PagingAndSortingRepository which inherits from CrudRepository . In reactive Spring Data, we only have ReactiveSortingRepository which inherits from ReactiveCrudRepository . How could we make pagination in a reactive way ? Will we able to make this in future with ReactivePagingAndSortingRepository for instance? Reactive Spring Data MongoDB repositories do not provide paging in the sense of paging how it's designed for imperative repositories. Imperative paging requires additional details while fetching a page. In particular: The number of returned records for a paging

Consider the following code: internal class Program { private static void Main(string[] args) { var client = new TcpClient(); client.ConnectAsync("localhost", 7105).Wait(); var stream = client.GetStream(); var observable = stream.ReadDataObservable().Repeat(); var s = from d in observable.Buffer(4) let headerLength = IPAddress.NetworkToHostOrder(BitConverter.ToInt16(d.ToArray(), 2)) let b = observable.Take(headerLength) select b.ToEnumerable().ToArray(); s.Subscribe(a => Console.WriteLine("{0}", a)); Console.ReadLine(); } } public static class Extensions { public static IObservable<byte>

I have a paginated response from an URL, I want to keep on hitting the next page URL which I get from the previous response and keep on collecting items till I don't have a "nextPage" URL in my response. How to achieve this in a reactive way using spring boot WebClient from WebFlux with out blocking? Request1: GET /items response: { items: [...] nextPage: "/items?page=2" } Request2: GET /items?page=2 response: { items: [...] nextPage: "/items?page=3" } Request3: GET /items?page=3 response: { items: [...] nextPage: null } Here I have created mock urls https://karthikdivi.com/apps