[gst-devel] shout2send nonblocking i/o?

[marco]

hi, 
i would like to know if there are any known drawbacks by having
shout2send using nonblocking i/o libshout. I am asking this cause i am
trying to develop a simple tool to stream audio to an icecast server and
i have a pipeline with two outputs, a shout2send and an alsasink
element. 
as soon as i experiment connection problems, the whole pipeline stalls.
i think this is due to the shout2send blocking on the shout_send() call
when there are network problems. 
I am playing a bit with the shout2send code and modified it to add a
nonblock parameter to enable a nonblocking behaviour.
basically, every shout_send() is followed by a shout_queuelen() (which
tells the size of the send queuelen). when the size returned by
size_queuelen() is beyond a certain threshold (totally heuristic :| )
we 
close the shout connection with a shout_close()
try to reconnect calling gst_shout2send_connect() again.

i am testing this code and it seems to work fine (no, i am not saying it
is beautiful and perfect, probably it's awful).
anyone interested in it?

sorry if this is the wrong list

marco