Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 22 06:20
    ankit-iod closed #396
  • Oct 22 06:20
    ankit-iod commented #396
  • Oct 22 06:16
  • Oct 21 17:23
    mbabker commented #396
  • Oct 21 06:58
    ankit-iod opened #396
  • Oct 19 18:52
    YosraHamza closed #395
  • Oct 19 18:52
    YosraHamza commented #395
  • Oct 18 21:50
    mbabker commented #395
  • Oct 18 18:33
    YosraHamza opened #395
  • Oct 09 22:06
    YosraHamza closed #394
  • Oct 09 22:04
    YosraHamza commented #394
  • Oct 09 22:04
    YosraHamza commented #394
  • Oct 09 21:29
    mbabker commented #394
  • Oct 09 21:21
    YosraHamza commented #394
  • Oct 08 22:57
    mbabker commented #394
  • Oct 08 19:44
    YosraHamza opened #394
  • Oct 01 01:51
  • Sep 25 01:04

    mbabker on master

    Fix a couple of issues found wi… (compare)

  • Sep 25 00:51

    mbabker on master

    Fix test namespace Remove unused dependency The RpcDispatcher effectively o… and 2 more (compare)

  • Sep 25 00:18

    mbabker on master

    Fix doc block Merge branch 'master' of github… (compare)

Aistis
@aistis-
Hello, I am trying to implement some notifications in my app. The goal is to have a user real time notices about process in back-end. For example: the server wants to inform user with a popup flash message about new event (friend request, new message etc.). I have successfully launched websocket server and registered periodic service every 0.5 of sec. I believe this service should do foreach for all active clients fetching the messages from MySQL and should notice the client if exists any. Do you think is it a good idea or you would suggest something more clever? The key things are, that the system should use MySQL for messages and it could hold ~30k active users with low latency...
The front-end is using angular, but I do not sure yet how it will implement WebSockets (natively or whatever)
Parham Doustdar
@parhamdoustdar
Hi!
Johann Saunier
@ProPheT777
hey
Parham Doustdar
@parhamdoustdar
I'm sorry for asking so many questions. I hope I'm not being a bother. This is my first time contributing to a Symfony bundle and I'm not sure about the workflow. So if you think I could do things another way anywhere during our conversation, just let me know.
Johann Saunier
@ProPheT777
no problem, there is no special workflow to contribute on 3rd party :D
to be honest I never used ZMQ as transport to push on websocket server
Parham Doustdar
@parhamdoustdar
So, I have a problem with the way you proposed.
Johann Saunier
@ProPheT777
we just need to be sure where we go and have the same global idea.
so speak about it !
Parham Doustdar
@parhamdoustdar
Ah, nice! :)
ZMQ is the only thing in the list that you mentioned in your comment that requires PHP to also start a server. So the gos:pusher:server will need to start two servers: one for zero_mq itself, and another for the pusher server.
Johann Saunier
@ProPheT777
no
pusher server and zmq is the same thing
zmq is just a technology to handle that
but inside pusher server you can zmq or another technology to do transport
like in websocket bundle
you can run different app with one server
here it's the same, you can run different transporter with the same command
Parham Doustdar
@parhamdoustdar
Hmm, I'm new to this and maybe I'm getting this wrong, but in this tutorial there are two servers. Look at the last section that says "creating our executable".
One is on port 5555, another is on 8080.
Johann Saunier
@ProPheT777
yes 8080 is the websocket
5555 is ZMQ (push server)
Parham Doustdar
@parhamdoustdar
Right. And which one does gos:push:server start?
Both?
Or do you have to run gos:push:server and then run gos:websocket:server?
Johann Saunier
@ProPheT777
you run both yeah
pusher server is isolated of websocket
Parham Doustdar
@parhamdoustdar
Well, the problem here is two things. First, you only need to start a pusher when you're using ZMQ. Things like Redis already have their own server.
Right?
Parham Doustdar
@parhamdoustdar
@ProPheT777: And the second problem is, the pusher that you pass into the stack (which I'm guessing would be a topic in our case) needs to be shared between the two instances, because the Redis client or the ZMQ server require a callback for their onMessage() function.
@ProPheT777: This is what has me confused: we can't have two different instances.
Johann Saunier
@ProPheT777
For today we don't care about other tech than ZMQ
we just must not closed the door for other
just focus on ZMQ implementation (with interface etc)
and the day where we need other support we will take the time to implement them