Small but important difference
the promise itself is a way of handling it
can this be a bit dangerous?
if we don't have a way of handling it, we don't have a way of controlling it
work after work
but not because you have the same works waiting for long time
this is when timeouts are important, I suppose
you lose that reference
in fact, you never have this reference
seems easy, but is not I think XD
I need to think about how to package everything around loggers for Drift
in a more enterprise way, like something plug and play (could be just a small set of existing handlers, and a bundle)
Keep in mind there are two different concepts of how promises/futures are driven. In Rust Futures surround around the pull concept (that means you need to drive them and pull work towards yourself). And the common Promise A implementation (ES6 Promises, ReactPHP Promises) surrounds around the push concept (that means they drive themself and push work forward).
@mmoreram Very interesting roadmap! Love to see how people in this chat have different ideas on how to solve this (me included) :) Looking forward to seeing what you come up with, I see a lot of potential for a DBAL/ORM :muscle:
Would be a shame if this end up being archived without anybody picking this up :(
(Shame on me for not getting back at these awesome projects in time - there are only so many hours in a day)
at least how I see the community and the growth path
does this project have a query builder?
Anyone familiar with Bunny know what the BC breaks or major changes were from v2 to v3 and v4? https://github.com/jakubkulhan/bunny/releases
@cboden jakubkulhan/bunny#66 suggests there are no significant changes between versions, but perhaps reply to this ticket? :)
Has there been any thoughts in separating protocol handling from components into their own packages, i.e. the HTTP protocol handling of react/http? I'm just thinking some parts could be refactored to allow it to be reused in other components or packages, instead of having to be re-implemented.
I mean, the MySQL protocol parser (incl. binary and text protocol values handler) could be refactored out of the Plasma MySQL driver too - I would literally support such a move, it's just I have no idea what the best way would be to do that, as hooking into the MySQL protocol is quite complex. But solutions for that challenge exist, I'm sure of that.