Re: Paging with REST::Client?

[sundialsvc4]

This node falls below the community's threshold of quality. You may see it by logging in.

[Argel]

For anyone curious, we're using a third party product that uses ISC DHCP under the hood. Any change to a DHCP scope requires a DHCP restart, and we have tens of thousands of scopes as we are a large enterprise grade company. Between broke/fix issues, new branches, and hardware refreshes that require scope changes, we have a lot of changes occurring in our environment. So updating 1800 scopes via the app's CSV bulk import process is tame and fully supported.

Reading between the lines from our vendor support, there are a couple race conditions that can occur when queuing up too many restarts. And as per above, we have a lot of changes going on daily. So after yet another disruptive outage last fall, I wrote a restart daemon that checks if a restart is needed and if so,is a restart in progress. If there is one in progress it skips restarting DHCP, if not then it restarts it. So now we rarely queue up any restarts (a queued up restart occurs when a restart is in progress and someone requests a restart).

Sundialsvc4, good intentions don't guarantee a good answer. Instead of asking for clarifications, you made a lot of incorrect assumptions and ran with them, resulting in an irrelevant post. Hopefully given the above you can see that some curiosity could lead to asking for clarifications, which in turn could lead to a useful response.

[marto]

"Hopefully given the above you can see that some curiosity could lead to asking for clarifications, which in turn could lead to a useful response."

Lower your expectations....

[1nickt]

Mike, do you ever compare your posts to the others on this forum? Do you notice any consistent qualitative difference?

It usually works great, but there are times when we are importing a ton of changes (e.g. 1800+) and I'm hitting the max amount of data REST::Client will accept.”

Okay, there’s your actual problem: throttling.

Wrong. Your analysis of the problem and your comprehension of the posts you are replying to is utterly wrong. The OP needs paging in handling a large HTTP response (as s/he well understood); it's nothing whatsoever to do with throttling requests to a server of any kind.

The rest of your comments, even if taken in the context of a discussion about throttling, are ignorant, vague, narcissistic, condescending, pompous and worthless all at the same time. Given your misunderstanding of what the topic even is, they are also irrelevant.

Suggestion: after a thought leaps into your head from 20 years ago and you craft one of your advice columns, before posting, open a separate window, re-review the thread you plan to reply to, and double-check whether you are at least speaking on the same subject.

[Anonymous Monk]

I'd suggest not taking any of the above to heart. One of your worst posts in a long time, though you managed to login this time around.