Please create an account to participate in the Slashdot moderation system


Forgot your password?

Comment The only problem is, it doesn't really work ... (Score 5, Informative) 233

... because the system simply sends a WAP push to a page which expires after a given period of time - the request is made over plain HTTP. The problem is that WAP gateways often choose to ignore the "no-cache" directives as do a lot of WAP browsers, which means that the message remains in the cache and can still be read both by the client and the gateways along the route after it has expired. A quick test we ran showed the messages being stored on the memory of a phone even thought it wasn't supposed to be cached. Also, it is always possible to simply save the page source to a different file on the phone.

A mobile software consultancy I work for is actually working on a project for a client which takes things a step further by encrypting the traffic from the server to the client and allowing the user to read it only via a J2ME MIDlet which never stores the messages to the RMS (persistent storage). For more information check out

The trouble with a lot of self-made men is that they worship their creator.