# Real-Time Phoenix: use PubSub with implementation of Phoenix.Socket.Transport rather than channels (page 37)

**URL:** <https://forum.devtalk.com/t/real-time-phoenix-use-pubsub-with-implementation-of-phoenix-socket-transport-rather-than-channels-page-37/42409>\
**Category:** PragProg Customers\
**Tags:** book-real-time-phoenix, question, websockets, phoenixsocket, pubsub\
**Created:** [25 February 2022 14:05 UTC](https://forum.devtalk.com/t/real-time-phoenix-use-pubsub-with-implementation-of-phoenix-socket-transport-rather-than-channels-page-37/42409 "2022-02-25T14:05:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sb8244](https://forum.devtalk.com/user_avatar/forum.devtalk.com/sb8244/32/209_2.png) [@sb8244](https://forum.devtalk.com/u/sb8244)\
**Post date:** [25 February 2022 18:31 UTC](https://forum.devtalk.com/t/real-time-phoenix-use-pubsub-with-implementation-of-phoenix-socket-transport-rather-than-channels-page-37/42409/2 "2022-02-25T18:31:57Z")

</div>

You will probably be successful with calling `PubSub.subscribe` inside of your Transport process. This will receive a handle\_info callback whenever an event is received over PubSub. You must subscribe to specific topics, which the book goes into detail about.

Think of PubSub as a layer that Phoenix provides. It sits below Channels, and Channels are built on top of it. If you don’t use Channels you can still benefit from PubSub because it’s a completely separate layer. You just need to call the right functions to use it.

---

_[View the full topic](https://forum.devtalk.com/t/real-time-phoenix-use-pubsub-with-implementation-of-phoenix-socket-transport-rather-than-channels-page-37/42409)._
