Hi,
On 6/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
With GLib mainloop it works the other way around: SU port integrates into
the mainloop as an event source. I don't know if custom event sources are
possible in libevent.
I don't understand your custom event sources. libevent provides all the
features of select/poll/epoll/... As long as select in su_select_port.c can
work for SU port, the libevent should work too, right?
Best regards,
Wensong
Best regards,
Mikhail
------------------------------
*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *ext wensong
zhang
*Sent:* Friday, June 29, 2007 11:09 AM
*To:* sofia-sip-devel@lists.sourceforge.net
*Subject:* [Sofia-sip-devel] changing sofia sip to use libevent?
We want to use sofia sip stack with our modules such as STUN, TURN and
ICE. Those modues use libevent library for event handling. We still like to
keep single-thread event-driven architecture.
There are probably two ways to integrate: one is to change those modules
to use sofia event loop interface, it seems some work; the other is to
change sofia to use libevent, though sofia has already supported the
select/poll/epoll/kqueue/devpoll event mechanism.
If I want to give a try to the latter, do I just need to make a
su_libevent_port.c file to hook up in libevent?
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
