-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jonathan,
On 3/2/2009 5:18 PM, Jonathan Mast wrote: > Thanks Ken, the problem with this solution is that these pages are for > viewing on mobile phones, most of which do not have JavaScript capability. > > What I had in mind was akin to what I do on regular website when I want a > link to generate a file that is saved to disk (an excel report app, for > instance). In this case, I set the Content-Disposition: to file or whatever > by calling method in the response object. Note that a full roundtrip happens in the above case: a regular HTTP request is sent to the server, and a full response is sent. The fact that the browser responds by saving the file and NOT refreshing the page is client-specirfic. > There must be something similar that can make the browser behave like it has > just clicked a regular TEL:NNNNNNNNNN link. What about accepting the request and responding with a REDIRECT to a tel:// URL? That would be the first thing I try. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmsXocACgkQ9CaO5/Lv0PCsCwCeMWIIe4RR1R4dDKAFwoDWqnTk 7fcAmQExGYVPkSGuZyT1tkbaE8lzbxma =0qLl -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
