This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I created a WAP application that enables any end-user(wap user) to select a midi file among a list of midi file (or link) and then listen to it. My problem is that the browser enables to the end-user to save that midi file onto HIS phone.
How do i do in order to enable the end-user(wap user) only to listen to the midi file (the link) and to prevent from saving the midi file onto his phone.
if I understand correctly, you have created a server-side application, and you currently access it with the device's generic wap browser. So a possible solution could be to create your own MIDP browser which does not support saving the files, and send the media files from the server only after a specific handshake or authentification operation (to prevent other browsers from accessing it).