referring to fig1 , there is shown a multi - device data distribution process , which may include a server - side process ( e . g ., server - side multi - device data distribution process 10 ) that may reside on ( in whole or in part ) and may be executed by ( in whole or in part ) server computer 12 ( e . g ., a single server computer , a plurality of server computers , or general purpose computer , for example ). alternatively / additionally , multi - device data distribution process may include a client - side process ( e . g ., client - side multi - device data distribution process 14 , 16 , 18 , 20 , 22 ), which may reside on ( in whole or in part ) and may be executed by ( in whole or in part ) a client electronic device , which may be a purpose - specific device dedicated to storing , distributing / receiving , and consuming media content , examples of which may include but are not limited to cable box 24 , television 26 , data - enabled cellular telephone 28 , personal media device 30 , game console 32 , a video projector ( not shown ), a digital video recorder ( not shown ), an in - car entertainment system ( not shown ), a dvd player ( not shown ), a network router ( not shown ), a network hub ( not shown ), a network switch ( not shown ), a cable modem ( not shown ), a movie projector ( not shown ), and a personal digital assistant ( not shown ). as will be discussed in greater detail below , multi - device data distribution process 10 , 14 , 16 , 18 , 20 , 22 may allow for the distribution of data files from a plurality of client electronic devices to a requesting client electronic device . server computer 12 may be coupled to network 34 , examples of which may include but are not limited to a distributed computing network ( e . g ., the internet ), a telecommunications network ( e . g ., a telephone network ), and a media distribution network ( e . g ., a cable television network ). server computer 12 may be a web server running a network operating system , examples of which may include , but are not limited to , microsoft windows xp server ™, or redhat linux ™. server computer 12 may execute a web server application , examples of which may include , but are not limited to , microsoft iis ™, or apache webserver ™, that allows for http ( i . e ., hypertext transfer protocol ) access to server computer 12 through network 34 . network 34 may be coupled to one or more secondary networks ( e . g ., network 36 ), such as a local area network , a wide area network , or an intranet , for example . additionally / alternatively , server computer 12 may be coupled to network 34 through secondary network 36 , as depicted with phantom link line 38 . the instructions and subroutines of server - side , multi - device data distribution process 10 , which may be stored on storage device 40 coupled to server computer 12 , may be executed by one or more processors ( not shown ), and by one or more memory architectures ( not shown ) incorporated into server computer 12 . storage device 40 may include , but is not limited to , a hard disk drive , a tape drive , an optical drive , a redundant array of independent disks ( i . e ., raid array ), a random - access memory ( i . e ., ram ), or a read - only memory ( i . e ., rom ), for example . users 42 , 44 , 46 , 48 , 50 may access server side multi - device data distribution process 10 , either directly though network 34 , or through secondary network 36 , using various client electronic devices ( e . g ., devices 24 , 26 , 28 , 30 , 32 ) coupled to at least one of networks 34 , 36 , e . g ., via a bidirectional network interface ( not shown ). as disclosed above , a client electronic device may be a purpose - specific device dedicated to storing , distributing / receiving , and consuming media content , examples of which may include but are not limited to cable box 24 , television 26 , cellular phone 28 , personal media device 30 , game console 32 , a video projector ( not shown ), a digital video recorder ( not shown ), an in - car entertainment system ( not shown ), a dvd player ( not shown ), a network router ( not shown ), a network hub ( not shown ), a network switch ( not shown ), a cable modem ( not shown ), a movie projector ( not shown ), and a personal digital assistant ( not shown ), for example . the various client electronic devices may be directly or indirectly coupled to network 34 and / or secondary network 36 . for example , cable box 24 and television 26 may be directly coupled to network 34 , via hard wired connections . further , cellular phone 28 may be wirelessly coupled to a cellular network / bridge 52 , which is coupled to network 34 . similarly , personal media device 30 may be wirelessly coupled to network 34 by wireless communication channel 54 established between personal media device 30 and wireless access point ( wap ) 56 ( which is coupled to network 34 ). game console 32 may be coupled to network 34 via secondary network 36 . wap 56 may be , for example , an ieee 802 . 11a , 802 . 11b , 802 . 11g , wi - fi , and / or bluetooth device that is capable of establishing secure communication channel 54 between personal media device 30 and wap 56 . the various ieee 802 . 11x specifications may use ethernet protocol and carrier sense multiple access with collision avoidance ( i . e ., csma / ca ) for path sharing . the various 802 . 11x specifications may use phase - shift keying ( i . e ., psk ) modulation or complementary code keying ( cck ) modulation , or example . bluetooth is a telecommunications industry specification that may allow , e . g ., mobile phones , computers , and personal digital assistants , to be interconnected using short - range wireless connection . as discussed above , the client electronic devices ( e . g ., cable box 24 , television 26 , cellular phone 28 , personal media player 30 , game console 32 , may each execute a client - side , multi - device data distribution process ( e . g ., client - side multi - device data distribution processes 14 , 16 , 18 , 20 , 22 , respectively ). client side , multi - device data distribution processes 14 , 16 , 18 , 20 , 22 may allow one or more respective users ( e . g ., users 42 , 44 , 46 , 48 , 50 ) to request and receive data files from one or more of the client electronic device and / or server computer 12 . client - side , multi - device , data distribution processes 14 , 16 , 18 , 20 , 22 may be stand - alone applications or may be modules , applets , or plug - ins that operate within other applications , examples of which may include but are not limited to web browser applications ( e . g ., microsoft internet explorer ™, mozilla firefox ™, and netscape navigator ™). client electronic devices ( e . g ., cable box 24 , television 26 , cellular phone 28 , personal media player 30 , and game console 32 ) may execute an operating system , examples of which may include but are not limited to microsoft windows xp ™, microsoft windows mobile ™, and redhat linux ™, for example . the instruction sets and subroutines of client - side , multi - device data distribution processes 14 , 16 , 18 , 20 , 22 , which may be stored on storage devices coupled to the respective client electronic devices , such as storage device 58 coupled to cable box 24 , and corresponding storage devices ( not shown ) respectively coupled to the other client electronic devices ( e . g ., television 26 , cellular phone 28 , personal media player 30 , and game console 32 ), may be executed by one or more processors ( not shown ) and one or more memory architectures ( not shown ) incorporated into the client electronic devices ( e . g ., cable box 24 , television 26 , cellular phone 28 , personal media player 30 , and game console 32 ). examples of the storage devices ( e . g ., storage device 58 ) may include , but are not limited to , a hard disk drive , a tape drive , an optical drive , a redundant array of independent disks ( i . e ., a raid array ), a random - access memory ( i . e ., ram ), a read - only memory ( i . e ., rom ), a compact flash ( i . e ., cf ) storage device , a secure digital ( i . e ., sd ) storage device , and memory stick storage device . referring also to fig2 , server - side , multi - device data distribution process 10 , client - side , multi - device data distribution processes 14 , 16 , 18 , 20 , 22 , or a combination of server - side , multi - device data distribution process 10 and client - side multi - device data distribution processes 14 , 16 , 18 , 20 , 22 may allow a user ( e . g ., user 42 of cable box 24 ) to request and receive a data file from a plurality of client electronic devices ( e . g ., television 26 , cellular phone 28 , personal media device 30 , or game console 32 ). additionally , the entire data file requested need not be provided by a single client electronic device . for example , two or more of the client electronic devices ( e . g ., television 26 , cellular phone 28 , personal media device 30 , and game console 32 ) may each have at least a portion of the requested data file stored on the respective storage device ( not shown ) coupled thereto . accordingly , two or more of the client electronic devices having the requested data file stored thereon may each transmit at least a portion of the requested data file to the requesting client electronic device ( e . g ., cable box 16 ). the data files that may be requested and received may include but are not limited to video files ( e . g ., television programming , feature films , sporting event broadcast ), audio files , videogames , electronic books , video lectures , software applications , software patches / updates for e . g ., television 26 , cellular phone 28 , personal media device 30 , and game console 32 , and the like . for example , multi - device data distribution processes 10 , 14 , 16 , 18 , 20 , 22 maybe used in connection with a media distribution service ( e . g ., a video - on - demand service ; not shown ) of which user 42 may be a subscriber . in such an example , the data files may be e . g ., video data files of movies and / or television programs that may be available through the video - on - demand service for downloading / viewing by subscribers , e . g ., user 42 . continuing with the above - stated example in which user 42 is a subscriber of a video - on - demand service that uses multi - device data distribution processes 10 , 14 , 16 , 18 , 20 , 22 for distribution of video files to subscribers , if user 42 wishes to watch the movie “ cinderella ”, user 34 may request the movie by inputting the title of the requested movie using e . g ., an input device such as a keyboard ( not shown ), a screen pointer ( not shown ), or a plurality of menus ( not shown ) in conjunction with a remote control configured to control e . g ., cable box 24 . additionally / alternatively , multi - device data distribution process 14 may be capable of transmitting scheduled requests for data files , e . g ., for requesting a recurring television program , or feature film on a specified date . multi - device data distribution process 14 being executed on cable box 24 may transmit 100 a request for the data file of the movie “ cinderella ”. transmitting 100 the request for the data file may include transmitting 102 the request for the movie “ cinderella ” to server computer 12 . server computer 12 may identify the client electronic devices coupled to networks 34 , 36 that contain at least a portion of the video data file for the movie “ cinderella ”. server computer 12 may e . g ., maintain a listing of the various client electronic devices coupled to networks 34 , 36 and the data files stored on each of the devices . based on the listing of client electronic devices and associated data files stored thereon , server computer 12 may , for example , identify television 26 and game console 32 as having at least a portion of the movie “ cinderella ” stored on the respective storage devices ( not shown ) coupled thereto . the listing of the data files maintained on the client electronic devices may be maintained e . g ., in a database on storage device 40 . examples of the database may include , but are not limited to , an oracle ™ database , an ibm db2 ™ database , a sybase ™ database , a computer associates ™ database , and a microsoft access ™ database . continuing with the above - stated example and in response to the request transmitted 100 , server computer 12 may e . g ., transmit an instruction / request to television 26 and game console 32 ( each of which contains at least a portion of the requested video data file ) to transmit the requested video data file of the movie “ cinderella ” to cable box 24 . additionally / alternatively , server computer 12 may transmit the location / identification ( e . g ., the ip address ) of each of the client electronic devices containing at least a portion of the requested video data file ( i . e ., television 26 and game console 32 ) to the multi - device data distribution process 14 running on cable box 24 . accordingly , multi - device data distribution process 14 may transmit a request for the video data file from cable box 24 directly to television 26 and game console 32 , which were identified by server computer 12 as containing at least a portion of the requested video data file . in a similar fashion , a listing of the data files stored on the various client electronic devices ( e . g ., cable box 24 , television 26 , cellular phone 28 , personal media device 30 , and game console 32 ) that are coupled to networks 34 , 36 may be maintained on each of the client electronic devices . for example , the listing of the data files stored on the various client electronic devices coupled to networks 34 , 36 may be stored in a database maintained on storage device 58 ( i . e ., the storage device coupled to cable box 24 ). examples of the database may include , but are not limited to , an oracle ™ database , an ibm db2 ™ database , a sybase ™ database , a computer associates ™ database , and a microsoft access ™ database . accordingly , multi - device data distribution process 14 may transmit 104 a request for the video data file ( e . g ., “ cinderella ”) directly to those client electronic devices identified ( within the database ) as containing at least a portion of the desired video data . according to another example , multi - device data distribution process 14 may transmit 106 the request for the desired data file ( i . e ., “ cinderella ”) to all of the client electronic devices ( e . g ., television 26 , cellular phone 28 , personal media device 30 , and game console 32 ) that are coupled to networks 34 , 36 . that is , multi - device data distribution process 14 may broadcast the request for the movie “ cinderella ” across networks 34 , 36 . the broadcast request may be received by any client electronic device coupled to networks 34 , 36 ( e . g ., television 26 , cellular phone 28 , personal media device 30 , and game console 32 ). by broadcasting the request , the necessary storage space required by each client electronic device may be reduced , and the overhead associated with maintaining and updating the list of client electronic devices may be eliminated . the speed at which data files may be distributed to a requesting client electronic device ( i . e ., the speed at which data files may be transmitted from transmitting client electronic devices and received by a requesting client electronic device ) may be based , at least in part , upon the upload speed of the transmitting client electronic devices and the download speed of the requesting client electronic device . often , the available upload speed of a network connection may be much slower than the available download speed . as such , the distribution speed of a data file transmitted from a single sender may be limited by the upload speed of the sender &# 39 ; s network connection . as such , the download capacity of the requesting client electronic device may be underutilized . the limitation on the distribution speed associated with a single sender may , at least in part , be overcome by multi - device data distribution processes 10 , 14 , 16 , 18 , 20 , 22 . multi - device data distribution processes 10 , 14 , 16 , 18 , 20 , 22 may increase distribution speed by concurrently transmitting the requested data file from a plurality of sources , i . e ., a plurality of client electronic devices each having at least a portion of the requested data file stored on their respective storage device . the aggregate upload speed of the plurality of transmitting client electronic devices may be greater than the upload speed of any single client electronic device . for example , four client electronic devices transmitting portions of a data file to a single receiving client electronic device at a rate of 100 kbps per upload connection may have an aggregate upload speed of 400 kbps . the foregoing upload speeds are provided for simplicity of explanation , and are not indicative of , or limiting on , actual usable upload speeds . the aggregate upload speed of the plurality of transmitting client electronic devices may better utilize the available download speed of the requesting client electronic device to achieve a faster distribution time . continuing with the above - stated example , television 26 and game console 32 may each have at least a portion of the movie “ cinderella ” stored on the storage device ( not shown ) associated with the respective client electronic device . respective multi - device data distribution processes 16 , 22 running on television 26 and game console 32 may each transmit at least a portion of the data file for the movie “ cinderella ” to multi - device data distribution process 14 running on cable box 24 . for example , multi - device data distribution process 16 may transmit 108 at least a first portion of the movie “ cinderella ”, which may be stored on the storage device ( not shown ) coupled to television 26 , to multi - device data distribution process 14 running on cable box 24 . similarly , multi - device data distribution process 22 running on game console 32 may also transmit 110 at least a second portion of the data file of the movie “ cinderella ”, which may be stored on the storage device ( not shown ) coupled to game console 32 , to multi - device data distribution process 14 resident on cable box 24 . as noted above , concurrent transmission of portions of the data file by each of multi - device data distribution processes 16 , 22 may yield an aggregate upload speed that is greater than the upload speed of either of multi - device data distribution processes 16 , 22 alone . being that it is not required that the transmissions be entirely concurrent , the distribution time for a data file may depend , at least in part , upon the number of client electronic devices transmitting at least a portion of the data file . the distribution time for a data file may be decreased by increasing the number of transmitting client electronic devices ( and , therefore , the aggregate upload speed ), up to the point at which the maximum download speed of the network connection / receiving client electronic device is realized . each multi - device data distribution process 16 , 22 transmitting 108 , 110 at least a portion of the requested data file may divide 112 , 114 the requested data file into a plurality of sub - portions . each of the sub - portions may be separately transmittable to the requesting multi - device data distribution process ( e . g ., multi - device data distribution process 14 ). dividing 112 , 114 the requested data file into a plurality of sub - portions , and separately transmitting the individual sub - portions may facilitate transmitting the requested data file via a plurality of multi - device data distribution processes . multi - device data distribution processes 16 , 22 may each transmit one or more sub - portions of the requested data file . the sub - portions transmitted by e . g ., either multi - device data distribution process 16 or multi - device data distribution process 22 may not account for the entire requested data file . however , the combination of the sub - portions transmitted by multi - device data distribution processes 16 , 22 may provide the entire requested data file . concurrently transmitting portions of the data file , e . g ., in the form of sub - portions , from a plurality of client electronic devices may optimize the available download bandwidth of the receiving multi - device data distribution process ( e . g ., multi - device data distribution process 14 ). in the above example , only two transmitting multi - device data distribution processes 16 , 22 have been discussed for illustrative purposes . however , more than two multi - device data distribution processes may concurrently and / or sequentially transmit at least a portion of the requested data file to the requesting multi - device data distribution process . the division of the data file into sub - portions by the transmitting multi - device data distribution process , e . g ., multi - device data distribution processes 16 , 22 may be coordinated by server computer 12 , e . g ., by multi - device data distribution process 10 running on server computer 12 . server computer 12 may determine e . g ., the size of the sub - portions into which the data file is broken , and which sub - portions are to be transmitted by the various multi - device data distribution processes . the size of the sub - portions may be the same , or may vary from one sub - portion to another and / or from one transmitting client electronic device to another . alternatively , server computer 12 may divide the data file into sub - portions prior to initial transmission of the data file , thus eliminating the need for the client electronic device to perform the file division process . if server computer 12 divides the data file into sub - portions , the divided file may be retained on the device receiving the divided file . accordingly , while the divided file may be assembled by the receiving device to facilitate e . g ., rendering of the divided file , a copy of the divided file may be maintained in a divided fashion to facilitate subsequent transmission of all or a portion of the divided file to another device . alternatively / additionally , the manner in which the data file is divided into sub - portions , the transmission order of the sub - portions , and the client electronic device transmission assignments may be determined by : the receiving multi - device , data distribution process ( e . g ., multi - device , data distribution process 14 ); the transmitting multi - device , data distribution process ( es ) ( e . g ., transmitting multi - device , data distribution processes 16 , 22 ); or the combination of the receiving and transmitting multi - device , data distribution processes ( e . g ., multi - device , data distribution processes 14 , 16 , 22 ). the dividing 112 , 114 of the data file into sub - portions and transmitting 108 , 110 the sub - portions may be accomplished according to pre - established rules , randomly , or a combination thereof . for example , the data file may be divided 112 , 114 into sub - portions based upon established rules , e . g ., based upon network characteristics and / or data file characteristics ( e . g ., total data file size and data file type ). similarly , the sub - portions may be transmitted in a prescribed order . for example , multi - device data distribution process 16 may transmit sub - portions corresponding to a first half of the data file and multi - device data distribution process 22 may transmit sub - portions corresponding to a second half of the data file . alternatively , multi - device data distribution processes 16 , 22 may transmit alternating / random sub - portions . dividing 112 , 114 the data file into smaller sub - portions may facilitate transmission of the requested data file by a larger number of transmitting client electronic devices . for example , a greater number of sub - portions ( e . g ., due to a smaller sub - portion size ) may allow a greater number of client electronic devices to transmit a portion of the data file without excessive redundancy . additionally / alternatively , smaller sub - portions may allow client electronic devices containing only a small portion of the requested data file to transmit one or more sub - portions of the data file . as noted above , the size of the sub - portions may vary from one sub - portion to another and from one transmitting client electronic device to another . therefore , a client electronic device having only a small portion of the requested data file may transmit the small portion of the requested data file , even if that portion is smaller than the sub - portions being transmitted by other transmitting client electronic devices . smaller sub - portions may also alleviate problems of redundant and / or overlapping portions of the data file . for example , if the data file is transmitted without coordination between the transmitting client electronic devices , redundant or overlapping sub - portions may be transmitted by each client electronic device . that is , each transmitting client electronic device may transmit the same sub - portion . smaller sub - portions may , at least in part , alleviate the efficiency loss resulting from redundant transmissions . for example , the redundant sub - portions may be smaller in size and / or less frequently occurring . multi - device data distribution process 14 may store 116 the requested data file on storage device 58 coupled to cable box 24 . storing 116 the data file may include receiving 118 at least a first portion of the data file from the first transmitting client electronic device ( e . g ., the portion transmitted by multi - device data distribution process 16 ) and receiving 120 at least a second portion of the data file from the second transmitting client electronic device ( e . g ., the portion transmitted by multi - device data distribution process 22 ). multi - device data distribution process 14 running on cable box 16 may assemble 122 the portions of the data file received from the various transmitting client electronic devices ( e . g ., television 26 and game console 32 ) to form the complete data file . assembling 122 the received portions of the data file may include , but is not limited to , creating and saving a single discrete file including the received portions and / or associating the received portions . creating a single discrete file including the received portions may include e . g ., ordering the received sub - portions of the data file ( e . g ., based on offset information ) and saving the ordered sub - portions of the data file as a single data file . associating the received portions of the data file may include e . g ., creating logical associations between the received portions based on offset information or other ordering characteristics . once the received data file has been stored 116 , multi - device data distribution process 14 may render 124 the data file . continuing with the above - stated example in which the received data file is a video data file of the movie “ cinderella ,” multi - device data distribution process 14 may , alone or in conjunction with one or more additional processes and / or hardware components , render 124 the movie “ cinderella ” either directly or in conjunction with an additional device ( e . g ., a television set ( not shown ) or display screen ( not shown ) coupled to cable box 24 ). alternatively / additionally , multi - device data distribution process 14 may otherwise make the received data file available for processing consistent with the nature of the data file ( e . g ., video file , video game , electronic book ). in an embodiment in which server computer 12 maintains a listing ( e . g ., in a database stored on storage device 40 ) of data files and / or client electronic devices upon which data files are stored , one or more of multi - device data distribution processes 10 , 14 may update 126 the list of data files and associated client electronic devices upon which the data files are stored . the updated list may facilitate the subsequent distribution of the received data file to other client electronic devices coupled to networks 34 , 36 from cable box 24 . similarly , multi - device data distribution process 14 may update any other listings of available data files and associated client electronic devices maintained , e . g ., on one or more of the client electronic devices coupled to networks 34 , 36 . as mentioned above , multi - device data distribution process 14 may be used in connection with a media distribution service , such as a video on demand service . some or all of the data files may be distributed at a fee . continuing with the above - stated example , one or more of multi - device data distribution processes 10 , 14 , 16 , 18 , 20 , 22 may charge 128 transaction fees for the requested data file ( e . g ., once the file has been received , when the file is requested , or during transmission of the file ). various transaction arrangements may be used e . g ., based on the specific content of the data file and / or the time of the transfer , for example . compensation may be made to the service provider . for example , in the context of a video on demand service , compensation may be made to the service provider for the content . additionally / alternatively , compensation may be made to the participating client electronic devices ( or owners thereof ), from which the data file was transferred . as discussed with reference to the above - stated example , the distribution time for a data file may be decreased as the number of client electronic devices ( which include at least a portion of the data file ) increases . as also described by the above - stated example , data files may come to be stored on the various client electronic devices as a result of the previous requests for the data file . for example , user 44 requested the data file for the movie “ cinderella ”, which was subsequently transferred to , and saved on storage device 58 of cable box 24 . accordingly , cable box 24 may also be available for subsequently distributing the data file of the movie “ cinderella ” to other requesting client electronic devices . as such , the number of client electronic devices capable of transmitting the data file of the movie “ cinderella ” has been increased as a result of the request from user 44 . popular data files ( i . e ., data files requested by many users ) may be stored , in whole or in part , on the storage devices of numerous client electronic devices . the distribution time for a popular data file may be relatively quick due to a large number of available transmitting client electronic devices . as more client electronic devices request and receive the data file , the distribution time may become quicker ( up to the maximum available download speed of a given network connection ) as the number of available transmitting client electronic devices increases . in addition to the natural propagation of popular data files resulting from multiple requests for the data file , one or more of the client electronic devices may also be prepared for the anticipated popularity of a data file . for example , once again in the context of a data file of a feature film , it may be expected that the video release of a movie will be extremely popular based on the performance of the movie during its theatrical release . prior to its availability for download , the data file of the movie may be placed on the storage devices of one or more client electronic devices . for example , server computer 12 may push 130 the data file to the storage device of one or more of the client electronic devices . for example , server - side multi - device data distribution process 10 , alone or in conjunction with client - side multi - device data distribution process 14 , may download the data file to cable box 24 , and store the data file on storage device 58 . once the data file is stored on storage device 58 , the data file may be available for download ( e . g ., immediately , on a specified date , at a specified time , and / or only to specific users ). users requesting the data file may receive at least a portion of the data file from the client electronic device to which the file was pushed , e . g ., cable box 24 . pushing 130 the data file to one or more client electronic devices may at least partially alleviate initial network congestion e . g ., resulting from the need for a single source transmission and / or multiple requests for a file that is available from only a relatively small number of client electronic devices . accordingly , pushing 130 the data file to various client electronic devices may alleviate / reduce bandwidth consumption and network congestion . for example , rather than initially relying upon a single source for downloading the data file , server computer 12 may push 130 the data file to multiple client electronic devices , thus making them available for transmitting the data file to requesting client electronic device . according to another aspect , one or more of server - side , multi - device , data distribution process 10 and client - side , multi - device data distribution processes 14 , 16 , 18 , 20 , 22 may control the access to , or distribution of , one or more data files . access to or distribution of a data file may be controlled based upon , but not limited to , data file content , distribution time frame , and requesting client electronic device . for example , a motion picture production company may provide an extended preview of a movie for e . g ., three weeks . the data file for the extended preview may be freely distributed to ( and between ) client electronic devices during the three week time frame . however , after the expiry of the three week time frame , the file may be restricted against further distribution and / or display . according to another feature of this disclosure , one or more of multi - device , data distribution processes 10 , 14 , 16 , 18 , 20 , 22 may enable real time , or near - real time rendering of a data file as it is being transmitted 108 , 110 . for example , again in the context of the movie file for “ cinderella ” requested by multi - device data distribution process 14 running on cable box 24 , multi - device data distribution processes 16 , 22 may each transmit 108 , 110 at least a portion of the data file for the move “ cinderella ” to cable box 24 . to enable real time , or near real time , viewing of “ cinderella ”, one or more of multi - device data distribution processes 16 , 22 may , in response to a specific request by multi - device , data distribution process 14 , transmit sub - portions of the requested data file corresponding to the beginning of the movie “ cinderella ”. as such , once the sub - portions have been received and stored , e . g ., on storage device 58 , the received portions of the data file may be rendered . real time ( or near real time ) rendering of the data file may be facilitated by coordinating the transmission of sub - portions of the data file by multi - device , data distribution processes 16 , 22 . for example , transmission of sub - portions of the data file may be coordinated to : reduce / eliminate redundant sub - portions ; to minimize / eliminate overlap of sub - portions ; and / or to provide alternating sub - portions from the transmitting multi - device , data distribution processes 16 , 22 . the transmission by multi - device , data distribution processes 16 , 22 may be coordinated by e . g ., multi - device , data distribution process 10 , multi - device , data distribution process 14 , or between transmitting multi - device , data distribution processes 16 , 22 . additionally , the size of the sub - portions may be relatively small to decrease transmission time of each individual sub - portion , thus reducing the time before the sub - portion may be rendered by cable - box 24 . a number of implementations have been described . nevertheless , it will be understood that various modifications and alterations may be made . accordingly , other implementations are within the scope of the following claims .