
February 3rd, 2007, 10:32 PM
|
|
Eager Mistic Beaver
|
|
Join Date: Dec 2006
Posts: 213
|
|
Quote:
Originally Posted by slickthug85
n e 1 got a list of advantages that mtp can do that ums cant?
|
In concept (until it is ratified as a new USB device class, just like MSC [UMS]), MTP is FAR supperior for the purposes of a media player due to a number of things:
- No overhead to the host computer of controlling another device. It is not much of a burden on current hardware, but it frees the process as it enables a number of other things:
- Independency of filesystem, literally every implementator could use any (and I mean any) filesystem on the device, as the host computer is not responsible for that filesystem, but the DAP's firmware, so this opens the door to having much more robust and better suited filesystems for these devices (for instance, one with journaling to avoid database corruption, better suited to make out the most out of the available space [better block management], faster reads, etc)
- The device and the PC work more like a network connection, like a network share over SMB (Windows shares), where one computer sends a series of commands along with the files to the other computer. The same is the basic principle here, your computer sends a series of commands through this protocol to your device, receives the files, adds metadata to the database, etc, based purely on these commands. The computer is not responsible for anything else than sending these commands, the device is entirely responsible of their execution, and even better, their interpretation and allocation and organization of the files and data structures.
- Gives the ability to better organize how a particular device works, with standard applications, the aim is to get the protocol into a new device class definition, so that any compliant OS and program could send commands to MTP devices just like virutally any OS is able to communicate with one another through the Internet using TCP/IP.
- With those bases, implementers can do pretty much anything. However this greatly depends on the implementation itself (not the protocol as such) and that the protocol gets ratified as a new USB Device Class, so implementation could be even wider.
If you know how does MSC/UMS work, you'll recognize the advantages MTP has over it (for DAP devices, of course).
__________________
Want to use your Clix on Linux? Check this
|