asked on May 27, 2026
Hello,
I was unable to add a comment to the following ticket, so I am leaving my additional questions here:
Thank you for your previous response. It was very helpful.
I have two follow-up questions regarding Flexmonster 3.0:
1. For the /select and /members requests, should we understand that they will still remain sequential by design in Flexmonster 3.0, with no current plan to support parallel execution?
2. For the pagination / lazy loading improvements in Flexmonster 3.0, could you share any tentative release timeline?
We understand that the exact date may not be fixed yet, but even an approximate timeframe such as the expected quarter would be very helpful for our planning.
Thank you again for your support.
Best regards,
⋅ May 28, 2026
Hello,
Thank you for reporting the issue with posting ticket replies. Our team has already resolved it.
Regarding your question regarding /select and /members requests, the new WebSocket-based protocol planned for Flexmonster 3.0 is an entirely new communication layer, so there will no longer be separate /select and /members HTTP requests in the current form. The new WebSocket-based protocol planned for Flexmonster 3.0 will allow loading members and data in parallel. In addition, for fields with a large number of members, we are introducing a search-based member filter that does not require preloading all members at once.
Lazy loading is already implemented in our prerelease version, which you can explore here: https://prerelease.flexmonster.com/
The Flexmonster 3.0 is in an active development stage, and while we cannot provide an exact release date, you can refer to our roadmap for approximate estimates for planned releases and upcoming features: https://prerelease.flexmonster.com/roadmap
Please let us know if you have any additional questions.
Best regards,
Maksym
