<HTML><FONT FACE=arial,helvetica><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2"><BR>
In a message dated 9/23/03 4:58:05 PM, preid@reidit.co.uk writes:<BR>
<BR>
<BR>
<BLOCKQUOTE CITE STYLE="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px" TYPE="CITE"></FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2">>I have one for my own needs, but I think a player for general use should<BR>
>come from the mother ship to maximize standardization and distribution.<BR>
><BR>
>Just curious: What would you like to do with a player than couldn't be done<BR>
>as a standalone?<BR>
><BR>
>Richard Gaskin<BR>
<BR>
I have produced a small number of CBTs for a UK government<BR>
organisation who need to validate all executables for security<BR>
reasons. Supplying a single player with add-on stacks makes life<BR>
easier in this respect. It is easier to persuade public sector<BR>
customers that they are only running a single program with<BR>
downloadable modules than it is to say they need to allow an<BR>
increasing number of new executables. They get twitchy about the<BR>
security implications of new EXE files!<BR>
<BR>
Also, it minimises network traffic if each client workstation has a<BR>
single player installed which is set up as the helper-app within the<BR>
browser so the user can download any of a number of CBT stacks<BR>
without having to download the player engine each time or have to<BR>
decide what to do with an executable (with attendant "security<BR>
warnings" from their browser!).<BR>
<BR>
Cheers<BR>
<BR>
Peter<BR>
</BLOCKQUOTE></FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2"><BR>
<BR>
Peter-have you got a sample player we could look at?<BR>
<BR>
Jack</FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2"></FONT></HTML>