docs/diploma

diff thesis/tex/2-MarketAnalysis.tex @ 148:5f7beb2142d6

small corrections
author meillo@marmaro.de
date Tue, 16 Dec 2008 14:09:23 +0100
parents 2c4673d983c3
children 0b17f6e5edae
line diff
     1.1 --- a/thesis/tex/2-MarketAnalysis.tex	Mon Dec 15 19:18:27 2008 +0100
     1.2 +++ b/thesis/tex/2-MarketAnalysis.tex	Tue Dec 16 14:09:23 2008 +0100
     1.3 @@ -110,7 +110,7 @@
     1.4  
     1.5  The easiest way of unified messaging is to base it on either email and convert all input sources to email messages (as attachments for instance) and store them in the user's mail box. Or use the telephone system as basis and convert text messages to speech. Both is no problem for asynchronous communication.
     1.6  
     1.7 -Finally a critical voice from Jesse Freund, who voted unified messaging on top of a hype list for \name{Wired.com}, ten years ago \cite{wired:hype}. His description of the technology ended with the humorous sentences: ``Unified messaging is a nice idea, but a tough sell: The reason you bought a cell phone, a pager, and a fax/modem is because each does its job well. No one wants to download voice mail as a series of RealAudio messages or sit through a voice mail bot spelling out email, complete with `semicolon dash end-parenthesis' for ;-).''
     1.8 +Finally a critical voice from Jesse \person{Freund}, who voted unified messaging on top of a hype list for \name{Wired.com}, ten years ago \cite{wired:hype}. His description of the technology ended with the humorous sentences: ``Unified messaging is a nice idea, but a tough sell: The reason you bought a cell phone, a pager, and a fax/modem is because each does its job well. No one wants to download voice mail as a series of RealAudio messages or sit through a voice mail bot spelling out email, complete with `semicolon dash end-parenthesis' for ;-).''
     1.9  
    1.10  
    1.11  %todo: have a result here?
    1.12 @@ -211,6 +211,10 @@
    1.13  
    1.14  Whether email will be the one surviving, or short message service, or another one, does not matter. Probably it will be \name{unified messaging}, which includes all of the other ones in it, anyway. \MTA{}s are a kind of software needed for all of these messaging methods---programs that transfer and receive messages.
    1.15  
    1.16 +\subsubsection*{Unified Communication}
    1.17 +Integration of asynchonous with synchronous communication channels is what Unified Communication is about. It seems not be possible to merge the two worlds on basis of email in an evolutionary way. As only a revolutionary change of the whole email concept would make it possible, it is best to ignore it. New designed technologies are usually superior to heavily patched and bent old technologies anyway. A general merge of synchronous and asynchronous communication has good chances to be fatal for email.
    1.18 +
    1.19 +Until Unified Communication will become reality---if ever---electronic mail has a good position, also as basis for Unified Messaging.
    1.20  
    1.21  
    1.22