ClankBundle wont fire onSubscribe

107 views Asked by At

I'm trying to implement ClankBundle to Symfony2 project.
When I Create a function to call from js it works well, though when I try to create onSubscribe function on Symfony2 it wont fire and I get not errors.
Btw, this check is on local environment running over Ubuntu
this is my code
config.yml -

clank:
    web_socket_server:
        port: 8080        #The port the socket server will listen on
        host: 127.0.0.1   #(optional) The host ip to bind to
    rpc:
        -
            name: "acme" #Important! this is the topic namespace used to match to this service!
            service: "acme_hello.topic_sample_service" #The service id.
        -
            name: "sample" #Important! this is the network namespace used to match calls to this service!
            service: "my_bundle.rpc_sample_service" #The service id.

services.yml -

  my_bundle.rpc_sample_service:
      class: MyBundle\RPC\SocketService

  acme_hello.topic_sample_service:
      class: MyBundle\Topic\MyTopic

MyTopic.php -

<?php

namespace MyBundle\Topic;

use JDare\ClankBundle\Topic\TopicInterface;
use Ratchet\ConnectionInterface as Conn;

class MyTopic implements TopicInterface
{

  /**
   * This will receive any Subscription requests for this topic.
   *
   * @param \Ratchet\ConnectionInterface $conn
   * @param $topic
   * @return void
   */
  public function onSubscribe(Conn $conn, $topic)
  {
    file_put_contents('/deleteme.txt', 'onSubscribe called \n', FILE_APPEND);
    //this will broadcast the message to ALL subscribers of this topic.
    $topic->broadcast($conn->resourceId . " has joined " . $topic->getId());
  }

  /**
   * This will receive any UnSubscription requests for this topic.
   *
   * @param \Ratchet\ConnectionInterface $conn
   * @param $topic
   * @return void
   */
  public function onUnSubscribe(Conn $conn, $topic)
  {
    file_put_contents('/deleteme.txt', 'onUnSubscribe called \n', FILE_APPEND);
    //this will broadcast the message to ALL subscribers of this topic.
    $topic->broadcast($conn->resourceId . " has left " . $topic->getId());
  }


  /**
   * This will receive any Publish requests for this topic.
   *
   * @param \Ratchet\ConnectionInterface $conn
   * @param $topic
   * @param $event
   * @param array $exclude
   * @param array $eligible
   * @return mixed|void
   */
  public function onPublish(Conn $conn, $topic, $event, array $exclude, array $eligible)
  {
    file_put_contents('/deleteme.txt', 'onPublish called \n', FILE_APPEND);
    /*
    $topic->getId() will contain the FULL requested uri, so you can proceed based on that

    e.g.

    if ($topic->getId() == "acme/channel/shout")
        //shout something to all subs.
    */


    $topic->broadcast(array(
      "sender" => $conn->resourceId,
      "topic" => $topic->getId(),
      "event" => $event
    ));
  }

}

js code -

var mysess;
    $(document).ready(function(){
        var myClank = Clank.connect("ws://localhost:8080");

        myClank.on("socket/connect", function(session){
            //session is an Autobahn JS WAMP session.
            mysess = session;
            console.log("Successfully Connected!");
            //the callback function in "subscribe" is called everytime an event is published in that channel.
            console.log('before subscribe');
            session.subscribe("acme/channel", function(uri, payload){
                console.log("Received message", payload.msg);
            });
            console.log('afte subscribe')
            session.publish('im publishing from js');
            mysess.publish("acme/channel", {msg: "This is a message!"});
//            mysess.unsubscribe("acme/channel");
//            mysess.publish("acme/channel", {msg: "I won't see this"});

        })

        myClank.on("socket/disconnect", function(error){
            //error provides us with some insight into the disconnection: error.reason and error.code
            console.log("Disconnected for " + error.reason + " with code " + error.code);
        })
    })
1

There are 1 answers

0
Jakub Pawlik On

topic and rpc are different config entries:

 topic:
    -
        name: "acme" #Important! this is the topic namespace used to match to this service!
        service: "acme_hello.topic_sample_service" #The service id.
 rpc:
    -
        name: "sample" #Important! this is the network namespace used to match calls to this service!   
        service: "my_bundle.rpc_sample_service" #The service id.