Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 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)

  • Sep 19 20:39

    mbabker on master

    Document that GosSocket.rpcCall… Document the rpcCall function (compare)

  • Sep 07 14:22
    rasool707 commented #251
  • Sep 03 20:05

    mbabker on master

    Tweak the DataCollectorCompiler… (compare)

  • Sep 03 19:46

    mbabker on master

    Use Symfony Flex to limit Symfo… Merge branch 'master' of github… (compare)

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
here is an exemple with redis as transport
may be it can be more concret to you and anderstand of what I talk about
Parham Doustdar
@parhamdoustdar
@ProPheT777: Exactly. Look at this example you sent me. It has both the client and the server. So both of them have to be done in one instance. In other words, the MessagableTopicInterface (the new interface I am going to define which has onMessage() on it) will be passed both to the transport (so that it can define the callback on it) and to the WampServer. So, when you run gos:push:server, t
$ProPheT777: That's what I meant with the command starting two servers.
here is a websocket on the host and port you defined, and also another socket listening on another address:port.
Johann Saunier
@ProPheT777
yes
Parham Doustdar
@parhamdoustdar
okay, I give up. :) I can't wrap my head around a good enough design to be able to do this. Is it possible for you to implement this whenever your time permits? I'll read your implementation and learn. :)
Johann Saunier
@ProPheT777
Yep if you want, I'll can look into this at the end of week and week end
Parham Doustdar
@parhamdoustdar
It would be very nice of you. Since I've looked into your package, i can just diff and see your changes and work on adding other transports, for example.
Johann Saunier
@ProPheT777
@parhamdoustdar I think i will dive into transport layer because AMQP is requested as pusher integration and on my side I use redis in pub/sub mode to push so we have 3 transporters at this time.
Parham Doustdar
@parhamdoustdar
@ProPheT777 Ah, no problem. I can add ZMQ as long as there is an example to go with.
Johann Saunier
@ProPheT777
finally I will have time this evening to work on it
Parham Doustdar
@parhamdoustdar
Awesome!
Johann Saunier
@ProPheT777
I just follow the tutorial and make first test with zmq
GeniusesOfSymfony/WebSocketBundle#39
that will dirty until that work
Cristhian Fernandez
@cristhianfernandez01
Hello!!
I was watching the PoC PullRequest # 39
In theory any class that represents a message must implement the interface MessageInterface . I see this as associate to AMQP.
Johann Saunier
@ProPheT777
Yes message is detached from the underlaying protocol. Currently i'm learning push integration with zmq, real abstraction / implementation will coming soon.
Cristhian Fernandez
@cristhianfernandez01
Okay, I will be aware of that. AMQP would be necessary to implement a method called onAmqpMessage. A query, the class Pusher / Message would be a wrapper of the message of protocol (AMQP, ZMQ or Redis)?