<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Hi Christian, yes, I also guess that it would be easier (and more valuable) to port my application to 0.10 - so I will take that route. Is there any sort of "Moving gstreamer applications to 0.10" guide around ? that would save me some time.. thanks & regards, David S. Christian F.K. Schaller wrote: <blockquote cite="mid1158685794.2308.81.camel@localhost.localdomain" type="cite"> <pre wrap="">Hi David, Yes, I think the gnomevfssrc is the only one. You might be able to cut down its dependencies by grabbing some of the patches Nokia made to gnomevfs to move it to dbus etc., from maemo.org. I have no idea how well this would work though and I fear you might end up doing more work that way compared to moving your app to 0.10 Christian On Tue, 2006-09-19 at 17:18 +0200, David SIORPAES wrote: </pre> <blockquote type="cite"> <pre wrap="">Michael Smith wrote: </pre> <blockquote type="cite"> <pre wrap="">On Tue, 2006-09-19 at 17:00 +0200, David SIORPAES wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi all, I am using gstreamer in an embedded environment with quite limited resources and I need to use gstreamer-0.8.12 for compatibility reasons with some applications. I need to instantiate a gst element that acts as a HTTP source but it looks like the only one that can do the job is the gnomevfssrc element. I would not like to bloat my system with all the gnome libraries this plugin depends on so I am trying to sort out an alternative. Old fashioned glib-based gsthttpsrc element is not there anymore, whereas the neon-based plugin "gstneonhttp" is only available in 0.10 "bad" plugins package. Is there any other solution I can look for before backporting the neon-based element to 0.8 ? any other hint ? </pre> </blockquote> <pre wrap="">You are, of course, welcome to write a new 0.8 element using libneon for your purposes. However, it's fairly likely to be better for you to upgrade your application(s) instead - 0.10 simply works a lot better, more reliably, and the existing plugins are generally more stable and better supported. Also, I doubt anyone will be interested in helping you with 0.8 at all - if you choose this route, you'll be entirely on your own. Mike </pre> </blockquote> <pre wrap="">Hi, thanks for your prompt reply. I will check the effort required to upgrade my gstreamer applications to 0.10 and move on. Can you confirm the only way to have an HTTP source in 0.8.12 is to instantiate a gnomevfssrc element ? thanks & regards, David S. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash <a class="moz-txt-link-freetext" href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV</a> _______________________________________________ gstreamer-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:gstreamer-devel@lists.sourceforge.net">gstreamer-devel@lists.sourceforge.net</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/gstreamer-devel">https://lists.sourceforge.net/lists/listinfo/gstreamer-devel</a> </pre> </blockquote> <pre wrap=""> </pre> </blockquote> </body> </html>