User-agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630)
By "recent" I mean POST 2.0.1 release - this is something we are working on
for the 3.0 DSS / QTSS release. The code for this stuff is currently only
available in the public CVS, and I don't believe we have posted the
documentation on it yet because it is still a work in progress, though if
there is interest, we may be able to post preliminary documentation in CVS.
Several people have requested the ability to replace the underlying file
system used by the streaming server with a custom file system, and have the
server and modules transparently use that file system. For instance, a
custom database or networked file system.
So what we did was put file system calls - open, read, seek, close, etc,
etc, as callbacks in QTSS API. We also added the ability to write a "file
system plug-in" for QTSS.
This makes the process of replacing the underlying file system used by QTSS
very easy - and therefore makes it very easy to plug the streaming server
into a variety of environments that don't necessarily support the POSIX file
system APIs.
Of course, module developers have to use these callbacks for this to work -
so we will be posting that documentation soon, and if you have any
additional questions / concerns, feel free to discuss on this list.
on 11/7/00 6:44 AM, Walt Dexter at email@hidden wrote:
> Denis,
>
> Why *must* File I/O go through the API callbacks? Is there something special
> happening, or does *must* really just mean "we really really think it
> should?"
>
> (And what does "recent versions" mean, exactly?)
>
> How about the case wherein the media content is not being kept in a normal
> file? It seems to me that one could write a module to, for example, allow
> the storage of the content in a database.
>
> Walt
--
Denis Serenyi
QuickTime Streaming Server Engineering
email@hidden
