I think existing programming languages have lack of general purpose listening mechanism for state changes or events to objects in memory. People write their own adhoc observer pattern or hook pattern. I think people are forced into polling because of the lack of mechanism. Webhooks are an example of solution as an integration pattern between separate services but I'm talking about within a process, page or program.
I am inspired by Smalltalk but with a twist: it is the pattern and sequence of interactions (such as events, states or messages) between MULTIPLE objects - all interacting - that are interesting.
Golang's and occams select operator is powerful for switching between events from different sources.
My idea: I want to be able to efficiently epoll_wait/uring a sequence of steps and state changes between multiple objects.
The idea is complex event processing for POJOs or objects and states.
Epoll for general purpose objects has usecases in efficient and scalable change detection in microservices, graphical user interfaces dirtychecking, job systems and workflow systems.
If you have a pull or push driven system and you want to adapt it, your hand might be forced into a substandard solution to add reactivity to an event or state or event sequence.
In integration testing, I see this problem. You can fire events in Javascript that your test runner can listen to, this is one solution to this problem but you have to build it yourself. You could hook into Redux state management. I have only created APIs for pages for interrogation for use by Selenium. But what I feel you want is state communication that isn't dependent on timing but efficient notification. (I don't want to use Selenium ExpectedConditions Wait for which is what I generally used to fix tests, there's a far more elegant solution)
I am inspired by Smalltalk but with a twist: it is the pattern and sequence of interactions (such as events, states or messages) between MULTIPLE objects - all interacting - that are interesting.
Golang's and occams select operator is powerful for switching between events from different sources.
My idea: I want to be able to efficiently epoll_wait/uring a sequence of steps and state changes between multiple objects.
The idea is complex event processing for POJOs or objects and states.
Epoll for general purpose objects has usecases in efficient and scalable change detection in microservices, graphical user interfaces dirtychecking, job systems and workflow systems.
If you have a pull or push driven system and you want to adapt it, your hand might be forced into a substandard solution to add reactivity to an event or state or event sequence.
In integration testing, I see this problem. You can fire events in Javascript that your test runner can listen to, this is one solution to this problem but you have to build it yourself. You could hook into Redux state management. I have only created APIs for pages for interrogation for use by Selenium. But what I feel you want is state communication that isn't dependent on timing but efficient notification. (I don't want to use Selenium ExpectedConditions Wait for which is what I generally used to fix tests, there's a far more elegant solution)
reply