I think that it would be useful to think about how this was going to work in comparison to the pipeline/tools that we have today.

I had originally that that this was a replacement for OpenFlowJ, but with OF1.3 support. OpenFlowJ really only provides OpenFlow data types, message serialization and deserialization. (There's also a simple controller in there, but really just to demo how you might use the OpenFlowJ library.) Instead, this looks like it provides significantly more functionality that that.

I think that's because it was trying to sit "logically below" the OpenFlow plugin project and so it needs to handle connections, version negotiation and the like. Instead, the current OpenFlowJ is actually just a static library which sits inside (or is just used by) the protocol_plugins.openflow bundle without actually sitting below it.

--Colin

controller-dev-bounces@... wrote on 08/05/2013 01:28:55 PM:
> From: michal.polkorab@...
> To: openflowplugin-dev@..., controller-
> dev@..., openflowjava-dev@...
> Date: 08/05/2013 01:39 PM
> Subject: [controller-dev] Openflow Protocol Library
> Sent by: controller-dev-bounces@...
>
> Greetings,
>
> I am sending you presentation used on Openflow Protocol Library meeting.
> We would like to hear your comments and questions regarding the
> project's architecture and design.
>
> Michal Polkorab[attachment "Openflow Protocol Library.pdf" deleted
> by Colin Dixon/Austin/IBM] _______________________________________________
> controller-dev mailing list
> controller-dev@...
> https://lists.opendaylight.org/mailman/listinfo/controller-dev