Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 15 18:58
    andreybolonin closed #199
  • Dec 12 11:12
    Logioniz commented #43
  • Dec 12 11:05
    Logioniz opened #73
  • Dec 12 10:58
    Logioniz commented #43
  • Dec 11 07:02
    WyriHaximus commented #36
  • Dec 10 23:12
    ethernidee commented #36
  • Dec 10 23:11
    ethernidee commented #36
  • Dec 10 23:09
    ethernidee commented #36
  • Dec 09 13:17
    jsor commented #155
  • Dec 09 00:22
    WyriHaximus commented #155
  • Dec 08 22:09
    clue opened #155
  • Dec 08 15:11
    clue closed #220
  • Dec 08 15:11
    clue commented #220
  • Dec 08 15:06
    clue labeled #220
  • Dec 07 10:41

    WyriHaximus on master

    Add .gitattributes to exclude d… Merge pull request #34 from ree… (compare)

  • Dec 07 10:41
    WyriHaximus closed #34
  • Dec 07 10:41

    WyriHaximus on master

    Add .gitattributes to exclude d… Merge pull request #75 from ree… (compare)

  • Dec 07 10:41
    WyriHaximus closed #75
  • Dec 07 10:41

    WyriHaximus on master

    Add .gitattributes to exclude d… Merge pull request #40 from ree… (compare)

  • Dec 07 10:41
    WyriHaximus closed #40
Marc Morera
@mmoreram
great!
Cees-Jan Kiewiet
@WyriHaximus
the promise is a way of HANDLING consequences of this work once it finishes ;)
Small but important difference
Marc Morera
@mmoreram
yes, the creation is the code inside the then
the promise itself is a way of handling it
can this be a bit dangerous?
Cees-Jan Kiewiet
@WyriHaximus
Why would it be dangerous?
Marc Morera
@mmoreram
I mean, having work inside the loop that never ends?
if we don't have a way of handling it, we don't have a way of controlling it
Cees-Jan Kiewiet
@WyriHaximus
shrug I have projects that run for weeks/months at an end
Marc Morera
@mmoreram
yes, but because oyou have tons of different works inside
work after work
but not because you have the same works waiting for long time
this is when timeouts are important, I suppose
Cees-Jan Kiewiet
@WyriHaximus
Yes and canceling promises as well :)
Marc Morera
@mmoreram
for example, what happens if in Monolog, a handler that connects to Redis breaks?
you lose that reference
in fact, you never have this reference
Cees-Jan Kiewiet
@WyriHaximus
Yes, or you cache the last 1000 items until connection succeeds
Marc Morera
@mmoreram
only the handler has it
Cees-Jan Kiewiet
@WyriHaximus
So what I do in my Docker images for my app is that I wait untill redis and such are up
Marc Morera
@mmoreram
well, yes, this is another story, the reconnection of redis, mysql and rabbit
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)
Cees-Jan Kiewiet
@WyriHaximus
Marc Morera
@mmoreram
actually using this factory method, yes
Cees-Jan Kiewiet
@WyriHaximus
:+1:
Charlotte Dunois
@CharlotteDunois
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).
Christian Lück
@clue
@WyriHaximus Belated reply, but cool, let me know when you're near Aachen in Germany and want to chat, need a couch or an office! :+1:
@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:
Christian Lück
@clue
@CharlotteDunois You've done some amazing work with plasma, especially when comparing this with our existing database drivers, there's so much from for improvement!
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)
Marc Morera
@mmoreram
I think that, as a community, we should make sure that a project like it is alive and
at least how I see the community and the growth path
does this project have a query builder?
Marc Morera
@mmoreram
That's great
Chris Boden
@cboden
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
Christian Lück
@clue
@cboden jakubkulhan/bunny#66 suggests there are no significant changes between versions, but perhaps reply to this ticket? :)
Chris Boden
@cboden
Thanks @clue
Cees-Jan Kiewiet
@WyriHaximus
@cboden FYI I've contacted Jakub about helping out maintaining bunny and getting changes/fixes in
Charlotte Dunois
@CharlotteDunois
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.
Cees-Jan Kiewiet
@WyriHaximus
@CharlotteDunois what parts are you thinking about? /cc @clue
Cees-Jan Kiewiet
@WyriHaximus
FYI I'm not against it
Charlotte Dunois
@CharlotteDunois
@WyriHaximus It was just a general thought, but an example would be the HTTP protocol implementations, i.e. request header parser, transfer encoding chunk classes, multipart parser. Or a different example would be the DNS protocol parser and dumper from react/dns.
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.
Charlotte Dunois
@CharlotteDunois
The RFC6455 library from RatchetPHP might be a good example of such a separated, reusable protocol handling package.