Hello Martin, This very good news! :)
One of the principles of NOX/OpenFlow is the emergence of new technologies (protocols, applications...). Then it would be good if the user can create their own space in the directory NOX. As a suggestion, it would be nice to have a small section in the next version (documentation) on this subject. Well I've done it here in our project (remove all our modules of the coreapps/examples directory) and had a little work, first because I needed to recompile the NOX, second because it did not work in the root directory (noxcore/src)(why?). I needed to create it within the (noxcore/src/netapps), ie: noxcore/src/netapps/myapps. For example, let's say that some team is working with data center, a workspace for your application would noxcore/src/dcapps and not noxcore/src/(coreapps|netapps|webapps)/dcapps, OK?! Atenciosamente, Macapuna - Unicamp On Mon, Nov 2, 2009 at 1:24 AM, Martin Casado <[email protected]> wrote: > Hi all, > > We're going to start preparing to put Nox 0.6.0 up on noxrepo. This > release will include significant improvements to the netapps > (authenticator, routing, topology), debugging, documentation, and OpenFlow > 1.0 wire support. Because there will be some changes to the API, we'll be > developing within a separate branch for the time being. > If anyone has significant outstanding patches that they'd like to see get > into 0.6, please let me know. The current 0.5 code base will not be > supported going forward. > Otherwise, this shouldn't disrupt any ongoing work. > thanks, > Martin > > _______________________________________________ > nox-dev mailing list > [email protected] > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > -- Carlos Macapuna
_______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
