HTTP via SMS is actually old, back in the short period in the 1990s when SMS was free in Germany, there were projects to do that. The big problem of course is that SMS is horribly expensive in most countries.
A project that's just landed on github aims to let users in the developing world access Web pages over text messages alone. It's not as absurd an idea as it might first seem, to those of us whose first-world-problems include “how do I delete the U2 album from my iTunes library?” While the number of mobile phones in the world …
Yes, you will still rack up the data charges, but the signal/noise will be INCREDIBLE!
@Charles 9, you've missed the point.
"TXT messages can carry 140 characters, at eight bytes a character, which is 1,120 bytes per message."
Most sensible character encoding uses eight BITS per character (=one byte).
But then most SMS systems support 160 characters per message. (presumably the other 20 are used as headers in this system? This could be clarified)
It should have been bits.
Though, the only two encodings I know in use by SMS messages are UCS-2 (16 bits * 70 characters) and GSM 03.38 (7 bits * 160 characters)...
While apparently there /is/ a mode for 8-bit bytes, it's meant for raw data and generally not used for regular text messages.
I hate web-mail forms in websites. They are even more fire and forget than email. They are just about acceptable if, and only if, there is an option to send a copy to me. If I make a complaint, query etc I would like a record of what I sent in my email client, not some eminently forgettable random txt file that I have saved somewhere on one of my disks.
Every phone that does MMS does exactly that.
At the time, with texts costing ~10p a go, WAP over SMS offered very little in the way of advantage over WAP over dialup, except for small data transfers where connectivity might be intermittant, such fire-and-forget packets used in Push messaging
Biting the hand that feeds IT © 1998–2019