<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">Hi, How hard it would be to implement bidirectional pads by extending GstObject class. The proposition is thus-- <pre class="synopsis"> <a href="http://library.gnome.org/devel/gobject/unstable/gobject-The-Base-Object-Type.html#GObject">GObject</a> +----<a href="http://library.gnome.org/devel/gobject/unstable/gobject-The-Base-Object-Type.html#GInitiallyUnowned">GInitiallyUnowned</a> +----<a class="link" href="http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer/html/GstObject.html" title="GstObject">GstObject</a> +----GstPad</pre> +----GstBidirectionalPad This class could be used for raw serial to TCP and vice versa conversion or modbus-RTU to modbus-TCP and vice versa conversion. We require these alongwith support for codecs etc in future(which GStreamer already provides). Warm Regards, Sourav On 13/06/13 16:28, Sourav wrote: </div> <blockquote cite="mid:51B9667E.6080402@netcommwireless.com" type="cite"> <pre wrap="">Hi, We are evaluating GStreamer framework to be used inside the codebase of our existing routers(Data Stream switch functionality). The requirements are as follows- Data stream switch to support at least the following from the get-go: o Raw mode (I.E normal Serial PADD) o Modbus GW/C o Should be written in an extensible way to support future file/port handlers and processing ‘codecs’. o Should have a basic UI for user configuration Possible future use cases could include: o USB Audio conversion to Flac codec, streamed to the internet via RTP over UDP o Analogue Telephone Port, to DTMF listener, with digits dialled streamed out to a TCP port in packet format (Raw, or maybe even RFC2833/SIP INFO) o Extensibility for future file/port handlers and codecs should be carefully designed and documented to support SDK users who may use this framework to add their own advanced functionality. One of the main concerns is for bi-directional data flows support and I suspect that existing solutions such as GStreamer tend to be one way as far as data flow is concerned. We will require bidirectional data flow for protocols like Modbus(req/rsp). Could bidirectional data flow be implemented in GStreamer? If so how? Also since the requirement is for embedded environments,hence how feasible it is to have GStreamer as part of out embedded router environment? Please send your response asap as that would let us choose to go or not to go with it. Time is a constraint and we want to decide asap. Warm Regards, Sourav ______________________________________________________________________ This communication contains information which may be confidential or privileged. The information is intended solely for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this communication in error, please notify me by telephone immediately. ______________________________________________________________________ _______________________________________________ gstreamer-embedded mailing list <a class="moz-txt-link-abbreviated" href="mailto:gstreamer-embedded@lists.freedesktop.org">gstreamer-embedded@lists.freedesktop.org</a> <a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-embedded">http://lists.freedesktop.org/mailman/listinfo/gstreamer-embedded</a> </pre> </blockquote> ______________________________________________________________________ This communication contains information which may be confidential or privileged. The information is intended solely for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this communication in error, please notify me by telephone immediately. ______________________________________________________________________ </body> </html>