Hi,

Maybe, more light reply is expected...

On 2012/01/13, at 19:21, <je...@zemarmot.net> wrote:

> Hi,
> 
> On Fri, 13 Jan 2012 16:34:58 +0900, HIro Suzuki
> <hiro.suz...@d3communications.jp> wrote:
>> Now we are going to prepare a new research project, called "RSi
>> Project" in Japan. "RSi" stands for "Realtime Service Initiative". In
>> this project we will provide new web site to share
>> Assoc. Prof. Ogashiwa's new codes as open source under the New BSD
>> Licence, and we are welcome to join to reserch / develop / deploy
>> activity with us. From this project, Assoc. Prof. Ogashiwa and
>> Mr. Sato in master course of Keio Univ. and I will join the next XMPP
>> Summit.
> 
> First of all, that looks like a nice project! And second, I have lived
> in Japan for a year and never saw any utilization of XMPP there, so
> that's good news. Do you know of other people/company/projects using
> XMPP?


 Unfortunately, XMPP wasn't popular in researchers and companies, but now
many people are being interested in real time local communications,
especially, in Japan, 3.11 earthquake arise some issues as follows...

---
1) Current network centric server / client system didn't work during a
national emergency.  So a local independent network like a city level is 
necessary.  In the daily use, these network will connect the Internet, and
will be useful for citizens's daily life. But in the emergency, these local
network will be work independently when the link to the Internet is cut.

 Current "Server Client Model" is tend to centralize functions in big "Data
Center", but in small local network like a city level can't utilize such a
big data center. So we needs more light weight service architecture like a
p2p model.

 I think XMPP Architecture will resolve this issue, because XMPP server, or
system doesn't need enormous functions in server side. 

2) Current "Web Services" in the Internet are not sufficient, in many case,
web services are lack of functions of realtime information exchange. For
example, Twitter provides realtime message exchange functions, but to utilize
Twitter service, Twitter needs big real time database at back end. And 
essentially "Web Architecture" is lack of paging function, or server can't
initiate communication path to any client devices.

 I think XMPP is very useful for direct communications between peoples, 
or between man and machine/sensor, even in a national emergency.
---

 As a result, I think XMPP has many chances to become popular in next few
years, and XMPP is key technology to utilize local realtime communications. 

Regards,
Yoshihiro Suzuki

Reply via email to