Re: GStreamer gnome-vfs question
- From: Christian Fredrik Kalager Schaller <Uraeus linuxrising org>
- To: Alexander Larsson <alexl redhat com>
- Cc: gnome-vfs-list gnome org
- Subject: Re: GStreamer gnome-vfs question
- Date: 27 Apr 2003 13:42:15 +0200
On Wed, 2003-04-23 at 09:45, Alexander Larsson wrote:
> On 22 Apr 2003, Christian Fredrik Kalager Schaller wrote:
> > Hi,
> > We have a bug in GStreamer bugzilla:
> > http://bugzilla.gnome.org/show_bug.cgi?id=104840
> > Which contain the following for a while now:
> > [ It would be great if the gnomevfssrc plugin could have some way of
> > discovering whether the currently opened stream is seekable.
> > ------- Additional Comments From Wim Taymans 2003-04-04 14:41 -------
> > Any ideas how the gnomevfs API exposes the seekable property, I can't
> > find a method. Opening the file with OPEN_RANDOM causes gnomevfs to
> > open the stream without an error but then it continues to read random
> > memory...
> > ]
> > If any of you guys know the answer to this we would really appreciate it if
> > you could add a comment on the bug so we could resolve the issue on our side.
> > Thanks in advance,
> > Christian
> Hmmm. This sounds strange. gnome_vfs_seek() should return
> GNOME_VFS_ERROR_NOT_SUPPORTED if you seek on a handle where its not
> supported. For local file-uris I don't see how it can read random memory,
> gnome_vfs_seek() just calls lseek().
> However, there is no "seekable" property you can read. Is there even a
> posix API we could use to implement this?
------- Additional Comments From Wim Taymans 2003-04-26 10:28 -------
lseek returns -1 when an error occured, you can check errno to find
out that it was a pipe/socket or fifo (ESPIPE) you were seeking on; I
would suggest to return _NOT_SUPPORTED in that case.
Christian Fredrik Kalager Schaller <Uraeus linuxrising org>
] [Thread Prev