turning now to fig1 of the drawings , there is shown a media server system 10 incorporating and implementing the streaming media delivery system and method of the present invention . the media server system 10 includes a media file server 12 connected to the internet 14 and / or other networks , and thence to at least one client 16 associated with a user , for streaming data from the media server 12 to the client 16 , such as any known type of computing device such as a personal computer or a hand - held computing device . the connections between the media server 12 , the internet 14 , and the client 16 may be by wired or wireless connections , or any combination thereof . the streaming data may include at least one of audio data , video data , multimedia data , text data , and / or any combination thereof in an appropriate format to be received and accessed by a user at the client 16 . the media file server 12 includes a frontside network 18 , an array 20 of at least one stream server subsystem ( ss ) 22 - 24 connected to a frontside network 18 , and a backside network 26 connected to an integrated cached disk array storage subsystem 28 including at least one network application storage ( nas ) device 30 , 32 . the media file server 12 is a high performance , high capacity , and high - availability network - attached data server configuration which provides the ability for multiple file systems to exist concurrently over multiple communication stacks with shared data access . the media file server 12 also allows multiple physical file systems to co - exist , each optimized to the needs of a particular data service . the media file server 12 is implemented as a dedicated network appliance , integrated with and / or operating with known network operating systems such that , other than its superior performance , the media file server 12 and its operation are transparent to the end user using the client 16 . the media file server 12 also provides specialized support for isochronous data streams used in live , as well as store - and forward , audio - visual applications . therefore , the media file server 12 is suitable for a wide variety of applications such as image or audio file repositories , internet radio , video on - demand , and networked video applications , in addition to high - end file server applications such as the network file system ( nfs ) and / or other access protocols , network or on - line backup , fast download , etc . nfs is a well - known ietf file access protocol standard , described in “ nfs : network file system protocol specification ”, sun microsystems , inc ., rfc 1094 , mar . 1 , 1989 . the disclosed streaming system and method , including the media file server 12 , are implemented on such known network - based systems such as the nfs , for example , as described in u . s . pat . no . 6 , 212 , 640 , which is incorporated herein by reference . nfs acts as a network server for network communications by providing basic file access operations for network clients . such basic file access operations include opening a file , reading a file , writing to a file , and closing a file . the clustering of the stream server subsystems 22 , 24 as a front end to the integrated cached disk array 28 provides parallelism and scalability . the clustering of random - access memory in the stream server subsystems 22 , 24 provides a large capacity cache memory for streaming media applications . each of the stream server subsystems 22 , 24 is a high - end commercially available computer , providing the highest performance appropriate for a stream server at the lowest cost . the stream server subsystems 22 , 24 are mounted in a standard configuration , such as a nineteen inch rack . in the preferred embodiment , the stream server subsystems 22 , 24 are implemented either with “ netra t1125 ” or “ ultrasparc - ii ” systems available from “ sun microsystems ”. in the preferred embodiment , a dual processor “ netra t1125 ” is used as the memory of the stream server subsystems 22 , 24 with , for example , about 2 gigabits of main memory , about 20 gigabits of local disk storage , about 300 mhz cpu , and between about two and five sets of 100 megabit ethernet ports . the number of the stream server subsystems 22 , 24 in the array 20 , their processor class , and the amount of random - access memory in each of the stream server subsystems 22 , 24 may be selected for desired performance and capacity characteristics , such as the number of concurrent users to be serviced , the number of independent multi - media programs to be accessed concurrently , and the desired latency of access to the multi - media programs , as described herein . load balancing is provided , for example , by a “ big / ip ha +” load balancing system available from “ f5labs ” in one or more of the stream server subsystems 22 , 24 or , separately , as a load balancing device incorporated in the frontside network 18 . the databases associated with the stream server subsystems 22 , 24 are implemented by an “ enterprise 4500 ” database available from “ sun microsystems ”, and running on an “ oracle 8 i ” database server available from “ oracle ”. in the preferred embodiment , about 10 cpus , each of which is running “ oracle ” databases , are included in the database servers , as described herein . in the preferred embodiment , each of the storage subsystems 30 , 32 is a “ network appliance 740 ” storage device available from “ network appliance ”, with about 1 terabyte of storage and two filer heads for fault tolerance . in the preferred embodiment , multiple “ network appliance ” storage devices 30 , 32 are connected to the backside network 26 via two gigabit ethernet cards . two “ cisco 6509 ” switch / routers , available from “ cisco systems ”, provide fault tolerant network connectivity and tcp / ip routing for the backside network 26 , with fail over and load balancing between the two switches . each “ cisco 6509 ” switch / router includes two supervisor engine ( sup ) cards with multilayer switch feature card ( msfc ), router cards , four 48 port 100 megabit cards , and two 16 port 1000 megabit cards . in the preferred embodiment the “ netra 1125 ” systems of the stream server subsystems 22 , 24 are also used to perform application serving , such as for the playlist and directory servers described herein , as well as operating a firewall and facilitating web serving . the media file server 12 may also include web servers , such as those web servers available from “ apache ”, which are implemented to include the ability to execute perl and server side code implementing “ java ”, available from “ sun microsystems ”. in the preferred embodiment , the media file server 12 includes an integrated cached disk array storage subsystem 28 and a plurality of stream server computers 22 , 24 linking the cached disk storage subsystem 28 to the data network 26 for the transfer of audio and / or video data streams . the media file server 12 may also include a controller server for applying an admission control policy to client requests and assigning stream servers to service the client requests . the disclosed streaming media delivery system and method described herein provide efficient operation of streaming using the media file system 12 having several component subsystems , as shown in greater detail in fig2 . in implementing the streaming media delivery system and method , the media file system 12 includes , in at least one of the stream server subsystems 22 , 24 , a directory server 34 which lists the programs that are available to stream , a stream database 3 6 , a streaming server 3 8 , a media database 40 which may be included in the storage systems 30 , 32 , an advertising insertion server ( ais ) 42 , and playlist server 44 including a database for storing information about each stream , such as playlist data 46 . in an example embodiment , audio data is delivered from the streaming media delivery system , and information about each song such as the artist , song title , and cd or album name are also delivered synchronously . a playlist server delivers information synchronized to playlist entries for display in the player browser window . it is to be understood that , while audio data is used herein to describe the operations of the disclosed streaming delivery system and method , data not limited to audio may also be stored , accessed , transferred , and / or streamed , such as video , multimedia , and text data and / or any combination thereof with or without audio data . in another optional aspect of the current invention , when a user connects as the first user to a given program , a respective streaming server 38 is assigned to deliver the program from a pre - allocated pool of free / available servers . this pool is started in advance , and remains running but unassigned until requested by a user . in the present invention , when a user attempts to connect to a stream that already has an assigned server , the user is routed to the existing server delivering that stream , with the exception of on - demand mode in which each user is assigned their own server . in the present invention , a clerk device 48 is responsible for routing incoming user requests to the proper streaming server 38 , and for assigning a respective streaming server 38 of the server subsystems 22 , 24 to programs . the directory server 34 creates a listing of the available stations and / or programs which can be selected by users of the streaming media system . when a program is selected , a player window 50 is created at the client 16 , which is an instance of the user &# 39 ; s preferred web browser . the player window 50 includes an instance of a “ thin client ”, such as a small application program , a “ microsoft activex ” control , or an applet , such as a “ java ”- based applet , implemented by an embeddable player 52 , such as an embeddable client mp 3 player , which can receive streaming media and present this media to the user at the client 16 . the streaming server 38 is responsible for the actual delivery of media data to users of the streaming media system . the streaming server 3 8 operates in several different modes and delivers data differently depending on its operating mode , as shown in fig3 . the streaming server 38 supports four major modes of broadcasting : live , relay , basic / looping , and on - demand . the core component of this service executed on the streaming server is a streaming application , which may be implemented in the “ nanocaster ” software available from “ live365 ”. the streaming application is written in the c programming language and runs on the “ solaris ” operating system available from “ sun microsystems ”. the streaming application is optimized to run hundreds or even thousands of stations simultaneously on a single streaming server cpu . the streaming application is server software running on the streaming server 38 which streams , in an example implementation , audio data contained in files , for example , in the mp3 format , to many clients 16 connected through the internet 14 . the streaming application may be used in several different ways . the most common instance of the streaming application is streaming in a basic / looping mode , also called “ easycast ” mode provided by “ live365 ”, in which the streaming application takes a pre - compiled playlist of audio files , and sequentially or randomly streams the data contained in those files to clients 16 connected over the internet 14 . in relay mode , the streaming application may also be used to relay audio broadcasts . the streaming application can be configured to act as a listener to an audio stream on the internet 14 , and to rebroadcast utilizing client handling and scalability provided by the streaming application . in live mode , the streaming application may be used to implement live broadcasts over the internet using client software to record , and to encode the audio to be broadcast by the streaming application . the streaming application manages the sending of the necessary amount of data to each client connected . the streaming application logs listener access , including the time connected , the audio software that the listener used to connect to the broadcast , and any cookie information passed on through an accessed website for such audio , such as the website at http :// www . live365 . com available from “ live365 ”. the streaming application logs the listener counts at the start and at the end of an audio clip . more specifically , the modes include basic / looping mode , in which a broadcast originates from locally stored files ; live mode , in which a live source is sent to the streaming application for rebroadcast ; relay mode , in which the streaming application grabs a source stream from elsewhere and rebroadcasts it ; and on - demand mode , in which the streaming application delivers a stream upon the selection of a specific individual . the streaming application is responsible for connecting listeners to a source and for keeping data flowing to the directory and playlist services . the vast majority of stations providing such services and programs operate in basic / looping mode , in which the streaming application streams a playlist of mp3 files hosted on the main file system , for example , through the “ live365 ” website . in relay mode , the streaming application actively reads data from a non -“ live365 ” ip address , whereas in live mode , the streaming application monitors or “ listens ” on a particular local ip address for a source data stream and retransmits any detected data stream . for basic / looping broadcasts , the streaming application reads a playlist file , opens the next mp 3 file to be streamed , and streams its contents to each active listener . the streaming application reads an id 3 tag from the mp3 file , and accesses or calls a playlist server providing a playlist service to keep the playlist server up - to - date . the streaming application also access or calls various directory service routines to keep the station directory database up - to - date . because the streaming server 38 handles both the content origination and delivery , the streaming server 38 knows both what it is playing and to whom it is playing , which uniquely enables the streaming server 3 8 to deliver customized audio content to its listeners while drawing on very few system resources when there are few or no listeners . the streaming application produces log files that can be analyzed and certified by independent third parties . these logs track which songs are played and to how many listeners . the streaming application provides a massively scalable backend solution for streaming , and natively supports current data formats , for example , the audio format known as mp3 . the streaming application is extensible to handle any future type of available audio or video formats . the streaming application interoperates with an extensive set of known streaming players such as the player 52 , and known software functions and tools to reach a diverse listener and broadcaster base . a plurality of instances of the streaming application are executed as individual processes , with each broadcast provided by a respective streaming application . the number of streaming applications that can run on one host may be limited , for example , only by the amount of memory present in the host computer and by any limitations of the host computer &# 39 ; s operating system . each broadcast is assigned a tcp / ip port , and so if one streaming application is having problems , only the broadcast corresponding to the problem streaming application needs to be restarted , and so not every broadcast on that computer with the problematic streaming application needs to be restarted . each instance of the streaming application has virtually no cpu impact when it is running , and each streaming application is optimized to handle , for example , over 2 , 000 concurrent client connections running in one process . as shown in fig3 a user selects , through the client 16 , the operation to be performed for streaming by setting a configuration in step 54 . depending on the setting , the streaming system and method enters the basic / looping state 56 , the live state 58 , the relay state 60 , or the on - line demand state 62 . in the first three of these modes ( basic / looping , relay , and live ), users of the streaming media system which are accessing a common stream all receive the same data . this data can be delivered via internet protocol ( ip ) unicast or multicast . however , in on - demand mode , each user receives an individualized stream delivered by unicast . accordingly , the streaming system and method performs step 64 to send common data , or performs step 66 to send an individualized stream . the streaming system and method then concurrently perform steps 68 - 74 to broadcast data such as audio data in step 68 , to monitor / listen for other clients 16 accessing the streaming system and method in step 70 , to interact with other services in step 72 such as third party audio data sources , and to monitor for load activity in step 74 to control the streaming , for example , in low or zero load operations as described herein . in basic / looping mode , the streaming server 38 operates from a stored playlist or a randomly generated playlist and , based on this playlist , retrieves files from the media storage system 28 and delivers this data over the frontside network 18 and the internet 14 to users at clients 16 of the service . in this mode , the program delivered by the streaming server 38 is always running , so any users that connect at a later time will join it in progress . the streaming server 38 cannot be paused in this mode . in live broadcasting mode , the streaming server 38 is delivered a stream from a live broadcasting tool which can either play a playlist from locally stored files , audio from a microphone or line in , or a mixture of these sources , and the streaming server 38 cannot be paused in this mode . in relay mode , the streaming server 38 takes a stream from another server and repeats it . the streaming server 38 cannot be paused in this mode . in on - demand mode , a stream such as an audio stream is delivered to each individual user that connects to the streaming server . the streaming server 38 retrieves files as needed by each user . users can pause and resume programs in progress when the streaming server 38 operates in this mode . additionally , in the preferred embodiment , delivery of synchronized data such as visual information ( cd cover art , artist information ), promotional materials ( i . e . banner advertisements , buttons ), and commerce opportunities ( buy the cd you are hearing , buy concert tickets for the current artists upcoming show ) is also delivered to the user , with such delivery being synchronized with the stream . much of this synchronous content is relevant to the audience of listeners / viewers before they connect to a stream . for example , a potential listener to a streaming radio station might be interested in finding streams currently playing a specific artist . however , unless the stream is active ( i . e . playing and using system resources ), the synchronous content is not generated or available . furthermore , the rights of web broadcasters such as “ live365 ” to deliver commercial content are governed in the united states by the digital millennium copyright act of 1999 ( dmca ). the dmca dictates the rules under which internet broadcasters can broadcast commercial content over the internet 14 . one of the requirements of the dmca is that the listeners should not be able to predict the playlist in advance . if a station has a static playlist , on - demand broadcasting is perfectly predictable . but simulated live broadcasting as implemented by current streaming servers scales with the number of broadcasters , not with the number of listeners , and therefore is infeasible for large systems in which there are many stations with no listeners . accordingly , since it is necessary for the data storage unit in a streaming system to store a large amount of data and to transfer data at high speed , a striping technique is usually employed with the data storage unit 28 , in which a disk array device is provided by combining a plurality of disk devices 30 , 32 , and data are sequentially stored over all the disk devices 30 , 32 by being divided into small blocks . in addition , the real - time streaming server 38 is required to be capable of continuing a supply of a connected stream , and restoring data without stopping the server operation , even when a disk device is disabled . for this reason , for the data storage unit of the real - time streaming server 38 , a fault detection device or technique , such as those known in the art , is used for detecting a disabled disk device , and a disk device exchange device or technique , such as those known in the art , is used for exchanging disks during the server operation . the client 16 or client device may be any known computing device for facilitating data access and use , such as playback of received media data including audio data , video data , etc . in a preferred embodiment , the client 16 includes a user &# 39 ; s receiving terminal ; a display device capable of receiving and displaying html , xml , and / or ascii text for display ; and a player such as the embeddable client mp 3 player 52 for receiving and playing streaming audio . this terminal of the client 16 connects via the internet 14 to a streaming media server system 12 having , in an example embodiment , web servers for delivering html data using a playlist window ; the streaming servers 38 for delivering real - time media data such as audio and / or video ; the directory server 34 which lists all available programs or streams which are available from the service ; the playlist server 44 for delivering non - streaming data synchronized with track listings in playlists using playlist data 46 ; and the advertising insertion server 42 which inserts audio and / or video advertising content into a stream at a preprogrammed frequency or to reach specifically selected users that are connected to the streaming server 38 . in accordance with the invention , the streaming media system includes a cached disk storage subsystem formed by the storage devices 30 , 32 of the array 28 , which may include the station database 36 and the media database 40 . the cached disk storage subsystem is responsive to media prefetch commands for staging data specified by a process from the disk array 28 of the cached disk storage subsystem to an allocated portion of the cache memory when the data are absent from the cache memory , and the cached disk storage subsystem is responsive to a fetch command for fetching data specified by the process from cache memory of the cached disk storage subsystem . the data specified for the prefetch command for the process are retained in the allocated portion of the cache memory from the time that the cached disk storage substation has responded to the prefetch command to the time that the cached disk storage substation responds to a fetch command specifying the data for the process . after the cached disk storage subsystem responds to the fetch command , the allocated portion of cache memory holding the specified data is freed for receiving different data so long as the cached disk storage substation has not yet processed a prefetch command in which the data have been specified by another process that has not yet fetched the data . a buffer memory may also be included , in the array 28 and / or in the streaming server 38 , for temporarily storing the blocks read out from the plurality of disk devices . control devices known in the art are used for reading out the blocks constituting the real - time stream data from the plurality of disk devices to the buffer memory , and for reading out the real - time stream data from the buffer memory , according to a request for the real - time stream data from the client 16 . transfer devices known in the art are also included for transferring the real - time stream data read out from the buffer memory to the client 16 through a network such as the internet 14 . in order to operate a streaming system and method most efficiently , streaming servers 38 with no client connections need not retrieve data from the storage system 28 . there are two methods used to operate in such conditions and so to achieve such efficiency : using a zero / no load method and using a low load method to control the streaming server 38 , for example , in response to monitoring the load conditions and / or current operations of the programs and clients , for example , in step 74 in fig3 . as shown in fig4 - 6 , which illustrate an example of the method of operation of an instance of a streaming application for a given program to perform steps 68 - 74 in fig3 the streaming server 38 implements an instance of the streaming application to open a media file in step 76 associated with the program , with the media file to be streamed to the accessing users / clients 16 . the streaming application then loops forever in step 78 to stream the media file in the manner determined by the selected mode , as described herein . however , the streaming server 38 monitors in steps 80 - 82 , to implement step 74 in fig3 to determine if anyone is accessing / listening to the streamed media file and to determine if anyone is accessing a playlist of the program , respectively . in step 80 , if no one is listening to the opened media file , the streaming application determines in step 82 if someone is accessing the playlist of the program including the media file . if no one is accessing the playlist and , as already determined in step 80 , is not accessing the media file , the streaming application performs no load processing in step 84 , shown in greater detail in fig5 . however , if someone is accessing the playlist in step 82 but is not accessing the media file as previously determined in step 80 , then the streaming application performs low load processing in step 86 , shown in greater detail in fig6 . after either of steps 84 - 86 , the streaming application proceeds to step 88 to determine if the end of the song had been reached , which may be one reason why listeners have stopped listening to the program , and then the streaming application breaks out of the endless loop in step 90 and closes the media file in step 92 . if the end of the song had not been reached in step 88 , the streaming application determines in step 94 a delay , for example , by deducting from the sum of one second plus the start time , the sum of the finish time and the time to execute the loop step 78 . the streaming application then executes a sleep or delay procedure in step 96 , for example , to re - synchronize the processing of the media file with the looping step 78 , and the method proceeds to step 78 . however , if it is determined in step 80 that someone is listening to the given program and its associated media file , then the streaming application determines in step 98 if the listener is accessing the song in the media file a last time through . if so , the streaming application reads the data of the media file to a data buffer in step 100 for streaming to the user at an associated client ; otherwise , the streaming application determines in the media file in step 102 where the streaming server should be , to read the data of the media file to the data buffer in step 100 to be streamed to the user at the associated client . after reading such data in step 100 , if the streaming application determines in step 102 that there is no data in the buffer , for example , if all of the songs in the program have been read out to the buffer , then the streaming application proceeds to steps 90 - 92 to break out of the loop and to close the media file , respectively . however , if there is still data in the buffer as determined in step 102 , the streaming application determines if the end of the song has been reached in step 104 . if not , the buffered data is written in step 106 to the requesting clients 16 ; that is , it is streamed to the clients 16 over the internet 14 and / or other network distribution devices , and the streaming application proceeds to steps 94 - 96 to continue looping in step 78 to continue to stream data to the requesting clients 16 , if available and if the load conditions have changed by user action ; that is , no long accessing or listening . otherwise , if the song has ended in step 104 , the streaming application prepares in step 108 for the end of the song / audio data , for example , by inserting an end - of - file ( eof ) code or other data into the streamed data for detection and action by the client 16 . the streaming application proceeds to step 106 to write the song data and / or the eof code to the clients 16 , and the streaming application proceeds to steps 94 - 96 . as described herein , the streaming application performs low or zero / no load processing in fig4 as described in greater detail in fig5 and 6 . referring to fig5 for zero or no load operation , for a given program having an associated stream or streams , no stream processing or directory delivery is performed at all by the streaming server 38 when there are no listeners / viewers for the particular program and its associated streams . in addition , the streaming application , executed by the respective streaming server 38 and associated with the particular program , does not attempt to read data from audio files for the particular program , but the associated streaming application keeps track of where the streaming application should be in that file . when a listener does connect , a calculation is performed to determine what track should be delivered to the user . the calculation is performed by using the stored playlist which includes the knowledge of the length of each track , the period of “ off ” time that is required to link one track with the subsequent one , and the time of the last connection to the stream which is recorded when the last person disconnects from the stream . the proper track to deliver is calculated by comparing the time since the last connection to the sequence of tracks in the playlist , and determining which track would have been playing if the stream had been playing continuously . this calculation method is used upon connection for the first listener / viewer when the server was idle for some period of time , but all subsequent connections are handled by the normal live streaming logic . when a user connects to the associated streaming application to access the particular program , the associated streaming application jumps to the position where it should be , and starts to broadcast from that point on . in normal usage patterns , this optimization gives an order of magnitude increase in scalability . accordingly , step 84 in fig4 is performed by the steps 110 - 116 in fig5 in which the streaming application stops delivery of the un - accessed playlist in step 110 , stops streaming the song in step 112 , and virtually advances through the media file , such as audio data representing a song , in step 114 , by calculating how long the media file has been streamed . the streaming application then calculates and stores in memory , in step 116 , the location or time - point of the user in the song , which is used in step 94 described herein . the streaming application then proceeds to step 88 in fig4 . similar to the no load processing method of fig5 the low load processing method is shown in fig6 in which the streaming server 38 does not run , but a memory or database associated with the streaming server 38 keeps track of information and synchronous data continues to be updated in real - time , which reduces the resources required to deliver this content by avoiding the need to read files from the file storage system , to move this data across the internal network , or to consume cpu time performing these operations . however , since the playlist 46 is being actively read from the playlist server 44 , a limited amount of cpu time is consumed reading this data and updating the synchronous data list . accordingly , step 86 in fig4 is performed by steps 112 - 118 , in which the streaming application continues in step 118 to delivery the playlist to the requesting / accessing user or client 16 , and the streaming application performs steps 112 - 116 , as described herein , to stop streaming the song yet track the location and / or time - point of the client in the song . the streaming application then proceeds to step 88 . the directory server 34 is periodically contacted by the streaming server 38 to report current listener counts and other data . when a very large number of servers are operated and these updates are frequent , a very high load can be imposed on the directory server 34 and the station database 36 in which the station / program data are stored . in the present invention , the streaming servers 38 only contact the directory server 34 when there are user connections or request to the streaming server 38 . additionally , when a large number of users are requesting access to the directory , a large number of pages ( html , xml , or ascii data ) need to be delivered . since many of these requests are repetitive , the current invention includes the caching of requests and results to eliminate repetitive queries from being submitted to the station database 36 and / or media database 40 . the playlist server 44 is contacted by the streaming server 38 whenever a new track or playlist entry begins playing . when a very large number of streams are delivered to a large number of users , a very large number of playlists must be generated . in the current invention , if a station has no connected users , the playlist need not be generated . to implement the disclosed stream delivery system and method described herein , the streaming application is constructed to implement known multithreaded technology that takes full advantage of smp computer architectures , which ensures that the streaming application can handle several tasks while providing un - interrupted audio delivery to its clients . each instance of streaming application may be integrated with the “ live365 ” website by sending periodic status to services built to interface with a central database . the streaming application can notify a service when it starts , when users connect and disconnect , and when the source changes . as shown in an example embodiment in fig7 an instance 200 of the streaming application is running , and uses known application program interfaces ( apis ) and known hypertext transfer protocol ( http ) interface technology to send updates . for example , the instance 200 of the streaming application operates an audio insertion server ( ais ) api to communicate with an ais 202 , operates a disk update ( du ) api to communicate with a du server 204 , and operates a playlist server ( pls ) api to communicate with a pls server 206 and so to interface with one or more databases 208 to serve a plurality of clients 210 in a client list 212 . in one embodiment , the pls api sends audio track information to the pls server 206 which tracks the id3 information contained in mp3 files . the pls server 206 and other services may be coordinated to supply matching banner advertisements to provide a consistent audible and visual experience . the streaming application supports a known ais api to communicate with an ais 202 to deliver an inserted personal online desktop ( pod ) software component , such as a window process and / or a “ microsoft activex ” control , either between audio clips or when a client connects , for example , to display a window or screen message having an advertisement . advertising campaigns can be coordinated with the ais 202 which tells the streaming application 200 what to play and when to play them . the streaming application 200 logs all relevant information including time played and listener count for individual insert pods . the streaming application 200 also allows the block of inserts to be augmented with a station identification ( station id ) set in the configuration file . the api associated with instances of the streaming application is a set of commands which may be sent to the streaming application to control the behavior of the streaming application or to query its current state . the streaming application api is the basis for communicating with media player technology to facilitate on - demand audio through software - generated players , for example , pop - up windowed applications for playing media through an internet browser . the api uses standard http url syntax , facilitating ease of construction of high level interfaces to control the streaming application . the api uses three handlers , each one has distinct functionality , and is separated by modes of authority , as shown in tables 1 - 3 herein . the admin handler is responsible for initialization of the streaming application to either load a new configuration or query the loaded configuration . the control handler is responsible for random access through a playlist or audio track and to mimic consumer grade compact disc players . the play handler is responsible for listen authentication on a stream . the streaming application has the ability to be used as an on - demand streaming server . the streaming application can be instructed to load a playlist of clips , and wait idle until a listener connects . in the on - demand mode and through the streaming application api , the streaming application may be controlled externally to skip forward or backward through an audio clip . in on - demand mode , the streaming application has the ability to jump to any song in a playlist . the streaming application may be instructed to set a session id for a broadcast , and the streaming application then starts the audio . on - demand mode may also provide restricted access to an audio stream according to session id . the streaming application api consists of a set of commands which may be sent to the streaming application to change its behavior immediately . the api is invoked through a standard http connection , making it easy to control . example api commands are shown in tables 1 - 3 . table 1 illustrates administrative ( admin ) commands , table 2 illustrates a play command , and table 3 illustrates control commands . [ 0131 ] table 3 session specifying this parameter with the same session value that was set by the admin interface will allow subsequent control commands to be executed . seek specifying this value in the integer range 0 - 100 will seek to position in the current audio track . stop reloads the playlist from the beginning , it is up to the client to close the connection , it will report to the clerk that the ip / port can be re - allocated if necessary . pause stops the stream and remembers the progress in the playlist and file , it reports to the clerk that the ip / port can be re - allocated if necessary . term same as stop , except that it reports to the clerk that the ip / port must be re - allocated . getplaylistlength this parameter will return the number of audio tracks in the current playlist . jumptoindex specifying a value greater than 0 and less than the number of songs in the current playlist queues up the song indicated by the index and jump to that song . songstat returns current progress of audio track in percentage , current audio track length in seconds , and current playlist index value . example : songstat . progress = 0 songstat . total = 170 songstat . index = 1 songstat . filename = swilson_plays_guitar . mp3 scriptsongstat returns current progress of audio track in percentage , current playlist index value and return code in javascript output . example : & lt ; script language = “ javascript ”& gt ; var icurrentpos = 9 ; var isong = 1 ; var iresponse = 0 ; var filename = swilson_plays_guitar . mp3 ; & lt ;/ script & gt ;