[reSIProcate] Question about implementing own Transport and Sip Stack Interactions

[Byron Campen]

	The DNS stuff does not use resip::Transport, it uses whatever the  
DNS backend (in this case, ares) uses. If you want your DNS  
resolution to use epoll, there might be a way to get ares to do that.  
Anyone know whether this is possible?

Best regards,
Byron Campen

>  Hi,
>
>    We plan to use epoll() for our application and sip
> stack fds instead of going the current select() way. I am
> assuming that if I implement my own transport this should
> be possible. I think I have mapped most of what needs to
> be done to implement the Transport interface, so the sip
> stack interactions are taken care of - one issue I am not
> sure about is the DnsStub object in the stack. Is it
> possible to drive that too through our own transport or
> do we have to implement an external DNS for it?
>
>     Does anybody have notes (dos/donts) for implementing
> an external Transport?
>
> Thanks,
> Sunitha.
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2423 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070312/78955c95/attachment.bin>