経験のある技術者なら、こういう作り方は危ういと直感するのではないか。「IPアドレスと利用者」というマッピングが、2か所（端末と「パケット交換機」を含む電話網側と、「セッション管理」サーバの2か所）で管理されていて、これらを同期しなくてはならなくなっており、片方で更新が滞ると何が起きるかわからないという点で不安になって、避けたくなるはずの設計ではないか。
要するに、「ドコモ独自のサービスアプリ認証」なるものは、Winnyプロトコル並の難読化にすぎない。
Rating
50
Translation / English
- Posted at 13 Jan 2012 at 13:05
For a experienced technician, doesn't it feel that a method like this is dangerous? Mapping of "IP address and user" is managed at two locations (twol locations of telephone side including terminals and "packet exchanger" and the server in charge of "session management"), and there shall be sychronized. If update at one side delays, what kind of problem will occur cannnot be predicted. This point is doubtful. When designning, it shoud be avoided, shouldn't it?
In a word, the "Docomo' s special service application verification" is just as difficult to read as the Winny protocal.
In a word, the "Docomo' s special service application verification" is just as difficult to read as the Winny protocal.
Rating
50
Translation / English
- Posted at 13 Jan 2012 at 13:11
An experienced engineer might think that this way of construction is very dangerous. The mapping of “IP address and user” is controlled at two sites (telephone network site containing a terminal and packet exchanger and site of “session control server”; these two sites must be synchronized. If one site does not work properly on “renewal”, you cannot forecast what happens. You would like, therefore, to refrain from using this system.
In a word, the “Service app certification that is Docono’s own” is merely an obfuscation to the level of Winny protocol.
In a word, the “Service app certification that is Docono’s own” is merely an obfuscation to the level of Winny protocol.
Rating
50
Translation / English
- Posted at 13 Jan 2012 at 13:21
Experienced developer could have easily know by his intuition that "this kind of design is dangerous". Relationship between IP address and user is managed at 2 points(Telephone network which includes devices and "Packet switcher", and "Session management" server), and both have to be synchronized. If the update of the other side is interrupted by something, nobody knows what would happen. Anyone would want to avoid this kind of design.
In other words, "docomo original certification system of service and application" is mere obfuscation as low level as Winny protocol.
In other words, "docomo original certification system of service and application" is mere obfuscation as low level as Winny protocol.
