>   
In python, just use twisted. If you're using C++ you'll probably want to
use the asynchronous event harness. Check out src/include/tcp-socket.hh.
.m

> Hi,
> Sorry for unclear question.
> To be simple, do you know how to implement a thread socket server
> within component?
> Sincerely for your help
> Kevin
>
> *From:* 魏骏翔 <mailto:[email protected]>
> *Sent:* Monday, January 25, 2010 10:11 PM
> *To:* [email protected] <mailto:[email protected]>
> *Subject:* [nox-dev] Add own defined event and event handler
>
> Hi,
> For my project, I hope to let the normal switch component provide
> another socket or interface to users who want to configure the flow
> table entry.
> In order to achieve this, I have three possible methods.
> 1. make pyswitch component create another thread for socket server
> communication.
> problem: the component couldn't be successfully installed when nox
> start, because server thread always listening
> 2. create own defined event and event handler which could handle
> incoming request event
> problem: I didn't find out how to implement this
> I try to implement this function by means of normal thread and socket
> programming in python and then directly install the function in
> component. However, the component will always keep listening but not
> finish component installation. This means nox isn't successfully
> started up. Just like the status of pyloop component.
> Does anybody has some thought on this problem?
> Best regards,
> Kevin
>
> ------------------------------------------------------------------------
> _______________________________________________
> nox-dev mailing list
> [email protected]
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
> ------------------------------------------------------------------------
>
> _______________________________________________
> nox-dev mailing list
> [email protected]
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>   


_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Reply via email to