<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">Good analysis. However, from a probablistic viewpoint the time-out problem is vanishingly small for a lightly loaded local network (that's why UDP works very well for machine control applications REF: sixnet protocol).<DIV><BR class="khtml-block-placeholder"></DIV><DIV>Pretty much give the perfomer the ability to get his files over to the server. If he is really worried about time-outs, the logical thing to do is to structure those chuck scripts to load the needed files prior to starting the sound emitting spork-ettes.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Jim<BR><DIV><DIV>On Feb 27, 2006, at 7:29 PM, <A href="mailto:chuck-users-request@lists.cs.princeton.edu">chuck-users-request@lists.cs.princeton.edu</A> wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><B>From: </B></FONT><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Ge Wang <<A href="mailto:gewang@CS.Princeton.EDU">gewang@CS.Princeton.EDU</A>></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><B>Date: </B></FONT><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">February 27, 2006 6:17:59 PM HST</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><B>To: </B></FONT><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">ChucK Users Mailing List <<A href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</A>></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><B>Subject: </B></FONT><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><B>Re: [chuck-users] file open semantics for clustered chuck</B></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><B>Reply-To: </B></FONT><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">ChucK Users Mailing List <<A href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</A>></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Hi!</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Since an important usage mode for chuck is analogous to a server for multiple performers, I'd like to suggest that the file open semantics be extended.</FONT></P> </BLOCKQUOTE><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Great idea, though there are certainly more issue to consider for remote operations, since they often aren't always as transparent as their interface advertises.<SPAN class="Apple-converted-space"> </SPAN>For example, network timeouts when retrieving a file need to handled.<SPAN class="Apple-converted-space"> </SPAN>Actually this seems to be part of a similar problem of pre-loading/chunking sound files to avoid interruption on large sound files.<SPAN class="Apple-converted-space"> </SPAN>So, we should probably add some options to control load behavior.</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">By simply extending the semantics for Chuck's "open" from expecting a file name, I suggest that it be a URL instead.<SPAN class="Apple-converted-space"> </SPAN>If the filename starts with http:// or ftp:// or other legal prefix, give the URL to a curl library for access.</FONT></P> </BLOCKQUOTE><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Cool.<SPAN class="Apple-converted-space"> </SPAN>The .open function already examines the path to catch "special" internal data (i.e. "special:glot_pop").<SPAN class="Apple-converted-space"> </SPAN>It would make sense to extend that to URL.<SPAN class="Apple-converted-space"> </SPAN>We just need to find a way to semi-gracefully deal with potential network timeout and lag.</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Thanks.<SPAN class="Apple-converted-space"> </SPAN>We shall look into this.</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Best,</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Ge!</FONT></P> </BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>