ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to implement a single HttpInterceptor to handle authentication, error logging, and request transformation, with design considerations, testing steps, and failure modes.
Goal: Verify if NgRx Effects that use mergeMap preserve the initiation order of concurrent HTTP requests when dispatching success/failure actions, and measure any resulting latency in state updates. Constraints: The ordering depends on the RxJS operator (mergeMap, concatMap, exhaustMap), NgRx Store version, and selector memoization; there is no built‑in guar
Goal: Determine how the interaction between NgRx Effects and Angular's HttpClient influences request‑latency when several Store actions are dispatched concurrently. Constraints: NgRx Effects process actions synchronously; the choice of mergeMap versus concatMap changes request ordering and concurrency, while the Store runs reducers on the microtask queue and
Problem Description Xamarin’s HttpClient relies on platform‑specific handlers (OkHttp on Android, CFNetwork on iOS). The default connection pool is opaque; no public API exposes its size or timeout. When many concurrent requests are issued, the pool may silently drop connections after a timeout, leading to intermittent failures. Unresolved Decision For proje
The goal is to decide whether the default maximum connections per route limit (currently hard‑coded to 20) for the Apache engine should be exposed through the HttpClient configuration API. Constraints include preserving backward compatibility, avoiding unintended side effects for users of other engines, and aligning the new setting with Ktor’s existing confi
angular
ngrx
android
ktor