Where communities thrive


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

  • Sep 03 19:39

    mbabker on master

    Use Symfony Flex to limit Symfo… (compare)

  • Aug 27 14:49
    mbabker commented #393
  • Aug 27 14:49

    mbabker on master

    Fix amqp connect order Update default routing_key Merge pull request #393 from al… (compare)

  • Aug 27 14:49
    mbabker closed #393
  • Aug 27 12:37
    alexismarquis opened #393
  • Aug 26 20:28
    mbabker closed #185
  • Aug 26 20:28
    mbabker commented #185
  • Aug 26 20:27
    mbabker closed #186
  • Aug 26 20:27
    mbabker closed #187
  • Aug 26 20:27
    mbabker commented #187
  • Aug 26 20:25
    mbabker closed #192
  • Aug 26 20:25
    mbabker closed #195
  • Aug 26 20:25
    mbabker closed #196
  • Aug 26 20:24
    mbabker closed #206
  • Aug 26 20:23
    mbabker closed #220
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)?
Johann Saunier
@ProPheT777
A wrapper will be created
Cristhian Fernandez
@cristhianfernandez01
Ah, you're right
The wrapper must implement the interface MessaggeInterface?
Or am I wrong again
Johann Saunier
@ProPheT777
yes it will implement MessageInterface but currently it's draft and dirty test
Johann Saunier
@ProPheT777
GeniusesOfSymfony/WebSocketBundle#39 updated with full zmq support
Cristhian Fernandez
@cristhianfernandez01
Very good !! I am glancing to learn how to do with amqp.
Johann Saunier
@ProPheT777
Big change will come with this feature, i'm replacing all ratchet stack by own from IOServer to WampServer.
The current way about we handle push integration is not acceptable since we are building a server
and push integration hack the internal process of ratchet by catching topic on his own side to be able to broadcast inside
Cristhian Fernandez
@cristhianfernandez01
Perfect. I will be aware of the changes you will make on the basis of the server stack
I have a question. AMQP support for what would correct ?, use php-amqplib or extension amqp php?
Johann Saunier
@ProPheT777
php amqplib extension, pure php implementation is slow
Cristhian Fernandez
@cristhianfernandez01
You're right, I'll go down that way, using php-amqp extension (written in C).
Johann Saunier
@ProPheT777
I have replaced Guzzle3 to Guzzle5 with psr7 from our own ratchet engine
and stop to store all connection / topic inside component itself
by delegating to storage service, that will allow us to store this in php, redis or whatever you want
Cristhian Fernandez
@cristhianfernandez01
Ok. A question, the new version will be stored in another repository?
Johann Saunier
@ProPheT777
nope,
just add a new repo to our new server stack engine
websocket bundle will be tagged as 2.0 and new dependency will be added to our new repo
to replace ratchet
Cristhian Fernandez
@cristhianfernandez01
Ah, ok
I will wait eager to see how will the new server implementation. Once I understand the architecture I will have an idea to help with AMQP.
Cristhian Fernandez
@cristhianfernandez01
How the new repository ServerEngine be called?
Johann Saunier
@ProPheT777
I have no idea :smile:
Cristhian Fernandez
@cristhianfernandez01
:smile:
Cristhian Fernandez
@cristhianfernandez01
What components will use to the new Server Engine?
Besides Guzzle5
Johann Saunier
@ProPheT777
Same as Ratchet just replace old guzzle by the new :)
ratchet is low coupled and don't need a lot of component, just architecture design will be reviewed to be more flexible and better structure
all StdClass disapear in favor of value object
Cristhian Fernandez
@cristhianfernandez01
Very good idea
Johann Saunier
@ProPheT777
Lot of work has been done, ratchet is rewritten at 60% currently i'm working on WampComponent and Connection will be again reviewed because he is still weak. Definitely I think rewritten ratchet was a very idea and brings me a lot. We will unlock a lot of feature (keep alive, pipelining topic, raw websocket (without wamp), binary data). I hope you will enjoy :smile:
Cristhian Fernandez
@cristhianfernandez01
Thank you very much for your effort. :clap: Your ideas are excellent. I would like to help you in whatever that I can. :smile:
Cristhian Fernandez
@cristhianfernandez01
Hello Johann, how are you going with the implementation of version 2.0 of the bundle ?
Johann Saunier
@ProPheT777
work is in progress
Johann Saunier
@ProPheT777
Too much problems and too long time to start from scratch new server stack so I have fork ratchet and work from it