<div class="gmail_quote">On Dec 29, 2007 3:10 PM, Andrei Tanas <<a href="mailto:andrei@tanas.ca">andrei@tanas.ca</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">> Speaking of which: does somebody want to take a look at how Myth<br>> handles file paths? If under Linux a network share can be mounted so<br>> it's accessible using the same path (like /home/mythtv/videos), it's
<br>> not possible to do so with Windows. This kind of messes things up,<br>> since MythVideo shares the same configurations between all machines in<br>> one system.<br>> Also, ':' is being treated as a separator, which makes it impossible to
<br>> use drive letters (which, coincidentally, is needed to use network<br>> shares).<br>><br>> Network shares can use UNC paths (\\servername\share) rather than drive<br>> letters.<br><br></div>Ugh, I know that, but it doesn't make it possible to map a directory on a
<br>Linux server and on Windows frontend so it's accessible to applications on<br>both systems using exactly the same path.</blockquote>
<div> </div>
<div>Well, given that Windows has no correlation to UNIX paths, there isn't any option either way that will provide that. Instead, a Windows frontend will have to have it's own paths to each folder which is really no problem as Myth already supports different paths to the same files AFAIK from frontend applications and if not, we will simply need some kind of table mapping a UNC path or drive letter to a UNIX path for translation. As far as non-frontend plugins go, the Myth streaming should work just fine as is shown by the other Windows based frontends.
</div>
<div> </div>
<div>Kevin</div></div>