<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I will definitely have to try that. Now I think I understand the benefits of that approach. Sending the data back is important.<div>I do have a question though. In the Swift user guide, it states: "CoG coasters provide<span style="font: 12.0px Helvetica"> <span class="Apple-style-span" style="font-family: Times; font-size: 10px; "><font class="Apple-style-span" face="Helvetica" size="3">a low-overhead job submission and </font></span></span></div><div><span style="font: 12.0px Helvetica"><span class="Apple-style-span" style="font-family: Times; font-size: 10px; "><font class="Apple-style-span" face="Helvetica" size="3">file transfer mechanism suited for the execution of short jobs (on the order of a</font><span style="font: 12.0px Helvetica"> few seconds) and the transfer of small files </span></span></span></div><div><span style="font: 12.0px Helvetica"><span class="Apple-style-span" style="font-family: Times; font-size: 10px; "><span style="font: 12.0px Helvetica">(on the order of a few kilobytes)."</span></span></span></div><div><br></div><div><span style="font: 12.0px Helvetica"><span class="Apple-style-span" style="font-family: Times; font-size: 10px; "><span style="font: 12.0px Helvetica">If I want to use coasters with longer jobs, with the transfer of large files, will that be a problem/be ill-suited with this approach?</span></span></span></div><div><span style="font: 12.0px Helvetica"><span class="Apple-style-span" style="font-family: Times; font-size: 10px; "><span style="font: 12.0px Helvetica">I know that our goal is to work with much, much larger files down the road, and much longer jobs.</span></span></span></div><div><br></div><div>Thank you both, Michael and Mihael, for your assistance in this matter. I really do appreciate it very much.</div><div><br></div><div><div>Regards,</div><div><br></div><div>Andrew Boyce<br></div></div></body></html>