Sure twisted uses a socket but I was talking about the event-driven scheme as opposed to the bit more involved manual socket handling. Matter of opinion I guess - just thought twisted might be easier for the developer, then again that might be the python fanboy in me talking:>
On Wed, Sep 8, 2010 at 3:30 PM, kk yap <yap...@stanford.edu> wrote: > Kyriakos, > > Do you mind expect the difference between twisted and socket? I would > think you need a socket in either case, just using twisted or not. > Frankly, I prefer commonly used functionalities to be implemented in > C/C++, where there is more room for laziness without impacting > performance. > > Regards > KK > > On 8 September 2010 15:27, Kyriakos Zarifis <kyr.zari...@gmail.com> wrote: > > If I recall correctly since last time I did something similar, you don't > > need to run() as there is a twisted reactor already running for NOX. > > (I've been thinking whether a socket is the right way for the messenger > to > > talk to external applications, and was considering using twisted > instead.. > > KK?) > > > > On Wed, Sep 8, 2010 at 2:51 PM, Norbert Ambrus <noramb...@yahoo.com> > wrote: > >> > >> Hi KK, > >> > >> thanks for your reply. I'm afraid I'm not a Swig guru but meanwhile I > had > >> the idea to open a tcp socket in my module and listen for commands > there. > >> The problem is that if I don't do the whole socket thing in a separate > >> thread, it blocks the rest of my module's command flow. And if I create > an > >> own thread for the socket, it won't work (I found an other topic in this > >> list that states that threads are problematic on nox modules). > >> An other option that was recommended, is to use twisted library, but as > >> far as I have seen, it also blocks the flow after running reactor's > run() > >> command. > >> I would be glad if you could give me a pointer in the right direction. > >> > >> Best regards, > >> > >> N. Ambrus > >> ________________________________ > >> From: kk yap <yap...@stanford.edu> > >> To: Norbert Ambrus <noramb...@yahoo.com> > >> Cc: nox-dev@noxrepo.org > >> Sent: Sat, September 4, 2010 1:15:01 PM > >> Subject: Re: [nox-dev] Remote controlling NOX modules > >> > >> Hi Norbert, > >> > >> messenger module in NOX does that. But the functionalities is not > >> exposed to Python. If you are a Swig guru, here's a patch we will > >> accept. > >> > >> Regards > >> KK > >> > >> On 3 September 2010 22:42, Norbert Ambrus <noramb...@yahoo.com> wrote: > >> > Hi, > >> > > >> > I was wondering whether there is a possibility to remote control > running > >> > NOX > >> > modules. > >> > Here is what I have in mind: > >> > A NOX controller is run with two modules (./nox_core -v -i ptcp::6633 > >> > module1 module2). Now I would like to have a program that is able to > >> > call > >> > several functions of these modules, e.g. to manipulate timeout > settings > >> > or > >> > to add flows to the system (the modules have appropriate functions for > >> > this). The communication should also be bidirectional, so the program > >> > can > >> > get a response from the modules and can react to possible errors if > the > >> > desired function call produced any. > >> > I already took a look at the nox-send-command.py and > nox-json-command.py > >> > but > >> > am not quite sure if they meet my requirements. > >> > > >> > Best regards, > >> > > >> > Norbert Ambrus > >> > > >> > PS: I'm using OpenFlow 1.0.0 and the modules are in Python if that is > of > >> > importance. > >> > > >> > > >> > _______________________________________________ > >> > nox-dev mailing list > >> > nox-dev@noxrepo.org > >> > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > >> > > >> > > >> > >> > >> _______________________________________________ > >> nox-dev mailing list > >> nox-dev@noxrepo.org > >> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > >> > > > > > > _______________________________________________ > > nox-dev mailing list > > nox-dev@noxrepo.org > > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > > > > >
_______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
