# repeat Published articles for repeat. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## One or two nameservers? DevFeed: [One or two nameservers?]() Original publisher: [Read original article]() Author: Geoff Huston Published: 2026-09-15T06:01:49Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Internet](), [Query (disambiguation)](), [Server](), [Caching]() Tags: [2026](), [africa](), [article](), [china](), [dns](), [europe](), [experiment](), [india](), [internet](), [ipv4](), [ipv6](), [measurement](), [measurements](), [recursive-resolver](), [repeat](), [responses](), [server](), [tech-matters]() ### AI overview This article reports an experiment testing whether serving a DNS zone with two authoritative dual-stack nameservers changes repeated queries. Compared with one nameserver, two nameservers increased the single-query completion rate from 58% to 71% and reduced the average queries per test from 3.43 to 2.57. ### Source excerpt Do multiple dual-stack nameservers increase or decrease repeat DNS queries? The results of this experiment were a complete surprise. ## Create animated stripes in Jetpack Compose DevFeed: [Create animated stripes in Jetpack Compose]() Original publisher: [Read original article]() Author: sinasamaki Published: 2025-12-05T18:11:39Z Content type: tutorial Language: en Sources: [sinasamaki]() Topics: [Jetpack Compose](), [Compose](), [Code]() Tags: [app](), [article](), [building](), [code](), [compose](), [design](), [how-to](), [jetpack-compose](), [learn](), [list](), [parameter](), [patterns](), [repeat](), [rotation]() ### AI overview A tutorial on creating and animating repeating stripe patterns in Jetpack Compose using gradients, color stops, tiling, offsets, and a helper function based on weighted colors, repetition width, and angle. ### Source excerpt Use default gradients to create mesmerizing patterns in your app ## Effective Kotlin Item 19: Do not repeat knowledge DevFeed: [Effective Kotlin Item 19: Do not repeat knowledge]() Original publisher: [Read original article]() Published: 2024-01-08T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Programming](), [data](), [Algorithm](), [business logic]() Tags: [algorithm](), [business-logic](), [code](), [programming](), [repeat](), [workshop-learning-programming]() ### AI overview This article explains why repeated knowledge in a programming project can be problematic. It connects copy-paste, DRY, WET, and Single Source of Truth practices, then distinguishes program logic from common algorithms based on how often they change. ### Source excerpt Why knowledge repetition is so problematic and how it relates to the single responsibility principle. ## Introducing Vectordrawable-Seekable DevFeed: [Introducing Vectordrawable-Seekable]() Original publisher: [Read original article]() Author: Alistair Sykes Published: 2020-05-11T13:35:28Z Content type: tutorial Language: en Sources: [Android & Tech News -- Medium]() Topics: [Android](), [media3](), [XML](), [Library](), [SDK]() Tags: [android](), [android-app-development](), [android-development](), [animation](), [how-to](), [library](), [material-design](), [play](), [repeat](), [rotation](), [screen](), [vector](), [xml]() ### AI overview This tutorial introduces the Vectordrawable-Seekable library for Android. It explains how Core-Animation and SeekableAnimatedVectorDrawable add pause and seek controls to animated vector drawables, then demonstrates creating vector, animation, and drawable XML resources and displaying the result. ### Source excerpt Using the new and improved AnimatedVectorDrawable to pause and seek your animations.AnimatedVectorDrawable Android SDK 21 introduced both the VectorDrawable and the AnimatedVectorDrawable. This allowed you to use vector assets within your app, and even animate them. They've iterated on these since then, but AnimatedVectorDrawable was still missing something. You couldn't manipulate and control the animation. There was no pause or seek functionality. Core-Animation The Android team has been hard at work backporting the framework Animator APIs. They have created a separate unbundled AndroidX library called Core-Animation. The Animator APIs have been around for some time. But they didn't provide the capabilities needed for this pause and seek functionality. So they needed to be unbundled and then iterated on. Vectordrawable-Seekable Once Core-Animation was available the Android team could create the Vectordrawable-Seekable library. This library revolves around the class SeekableAnimatedVectorDrawable. Under the hood, this class uses the AnimatorSet and subsequently Animator from Core-Animation. These provide the pause and seek functionality. How toCreate the vector Firstly, you need a vector asset of the image you wish to animate. This works best if it is simple and optimised. See these resources for information on optimising assets: - https://www.brightec.co.uk/blog/creating-vector-drawables-android - https://arturdryomov.dev/posts/optimizing-android-vector-images/ For this example I am going to use an Android: https://medium.com/media/c1f49ee65961374471c7019479d595cf/href This XML file should be placed in your res/drawable directory. Notice the group names, as these allow us to reference each part of the image later. Notice also the pivot points defined. These define the pivot around which rotation would happen. Create the animation To define the animation itself you can create another XML file. This defines an ObjectAnimator. https://medium.com/media/51350379510a257 ## Java 9 Flow API: arbitration and concatenation DevFeed: [Java 9 Flow API: arbitration and concatenation]() Original publisher: [Read original article]() Author: David Karnok (noreply@blogger.com) Published: 2017-09-27T12:55:00Z Content type: tutorial Language: en Sources: [Akarnokd - Advanced RxJava]() Topics: [Java 9](), [Java](), [API]() Tags: [api](), [arbiter](), [arbitration](), [concat](), [concatenation](), [concurrent](), [event](), [flow](), [flow-api](), [java](), [java-9](), [jdk](), [onerrorresumenext](), [publisher](), [repeat](), [request](), [retry](), [submissionpublisher](), [subscriber](), [subscription](), [subscriptionarbiter]() ### AI overview This tutorial explains how to implement subscription arbitration for Java 9's Flow API when concatenating multiple publishers. It addresses stack growth, remaining-demand accounting, concurrent requests and cancellation, subscription switching, and produced-item tracking. ### Source excerpt Introduction A very common task is to combine multiple sources, or more generally, start consuming a source once the previous source has terminated. The naive approach would be to simply call otherSource.subscribe(nextSubscriber) from onError or onComplete. Unfortunately, this doesn't work for two reasons: 1) it may end up with deep stacks due to a "tail" subscription from onError/onComplete and 2) we should request the remaining, unfulfilled amount from the new source that hasn't be provided by the previous source to not overflow the downstream. The first issue can be solved by applying a heavyweight observeOn in general and implementing a basic trampolining loop only for certain concrete cases such as flow concatenation to be described in this post. The second issue requires a more involved source: not only do we have to switch between Flow.Subscriptions from different sources, we have to make sure concurrent request() invocations are not lost and are routed to the proper Flow.Subscription along with any concurrent cancel() calls. Perhaps the difficulty is lessened by the fact that switching sources happens on a terminal event boundary only, thus we don't have to worry about the old source calling onNext while the logic switches to the new source and complicating the accounting of requested/emitted item counts. Enter SubscriptionArbiter. Subscription arbitration We have to deal with 4 types of potentially concurrent signals when arbitrating Flow.Subscriptions: A request(long) call from downstream that has to be routed to the current Flow.Subscription A cancel() call from downstream that has to be routed to the current Flow.Subscription and cancel any future Flow.Subscription. A setSubscription(Flow.Subscription) that is called by the current Flow.Subscriber after subscribing to any Flow.Publisher which is not guaranteed to happen on the same thread subscribe() is called (i.e., as with the standard SubmissionPublisher or our range() operator). A setProduced(long n) ## Better Parameterized Tests with Burst DevFeed: [Better Parameterized Tests with Burst]() Original publisher: [Read original article]() Author: Square Engineering Published: 2014-10-21T16:08:00Z Content type: tutorial Language: en Sources: [Jake Wharton](), [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [Testing](), [coding](), [Android]() Tags: [android](), [automated](), [bugs](), [business-logic](), [engineering](), [enum](), [enums](), [framework](), [generate](), [object](), [parameter](), [repeat](), [running](), [test](), [testing](), [tests](), [unit-test]() ### AI overview This article introduces Burst, an alternate data variation mechanism for JUnit tests. It explains how enum parameters can generate combinations of class-level and method-level tests, including support for JUnit 3 and Android's testing framework. ### Source excerpt An alternate data variation mechanism for JUnit tests.