[pox-dev] About messenger component and messenger.js

[Sulabh Bista]

Thanks for all the hints. Looking at openflow.of_service. Looks interesting.

--Sulabh Bista



On Thu, Nov 14, 2013 at 9:49 PM, Murphy McCauley
<murphy.mccauley at gmail.com>wrote:

> On Nov 14, 2013, at 6:15 PM, Sulabh Bista <sul4bh at gmail.com> wrote:
>
> Hello everybody.
>
> I am learning to use the messenger component. I referenced POXDesk to see
> some examples on how this could be used (together with the messenger.js
> library).
>
> Now, where do I look for commands (eg, list_switches, get_flow_stats,
> set_table) that we can use with messenger.js? Do we have a reference for
> that or where are they derived from?
>
>
> So those commands are provided by what messenger would call a messenger
> service.  The services are generally a POX component of their own (or
> possibly as part of another component).  In the pox.messenger package,
> there's the log_service which provides functionality for remotely
> interacting with the log.  There's also some little example services.
>
> The things you mentioned, for working with OpenFlow, are in
> openflow.of_service.
>
> Also the wiki mentions " The messenger by itself is really just an API,
> actual communication is implemented by *transports* ". What is transports
> here?
>
>
> Transports are how data is actually communicated.  See the messenger
> package in the source code... it contains ajax_transport, web_transport,
> and tcp_transport modules (the tcp_transport module in dart actually has
> two transports -- a passive/listening one and an active/connecting one).
>
> The messenger package has a fair amount of documentation in it.  I've also
> just expanded the messenger section of the manual (mostly with information
> in this email).
>
> -- Murphy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.noxrepo.org/pipermail/pox-dev-noxrepo.org/attachments/20131114/9f9efae9/attachment-0002.htm>