Wind Framework 1.0.3 Release Notes

Version 1.0.3 of the pure PHP coroutine Wind Framework introduces a new Chan class for intra-process coroutine messaging, enhances the message queue with Redis and Beanstalk drivers supporting massive consumer counts and timeout settings, and fixes several Beanstalk client command errors.

Laravel Tech Community
Laravel Tech Community
Laravel Tech Community
Wind Framework 1.0.3 Release Notes

Wind Framework is a pure PHP coroutine framework.

Framework core:

Added Chan class for intra-process coroutine message communication.

Message queue:

Based on Chan, provides a Redis driver that, within a single process using only two connections, supports thousands of consumer coroutines; this feature automatically enables when process concurrency is set above 2 and the driver supports it.

Beanstalk driver supports the reserve_timeout parameter to set a timeout for fetching messages.

Task handling supports a fail() method, allowing special processing after multiple retries and letting the user decide whether a failed message goes to a failure queue or is deleted.

Beanstalk client:

Fixed error when the reserve-with-timeout command reaches its timeout.

Fixed exception when reserve encounters a DEADLINE_SOON response.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

redisMessage QueueFrameworkcoroutineBeanstalk
Laravel Tech Community
Written by

Laravel Tech Community

Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.