Deprecated: Assigning the return value of new by reference is deprecated in /home/project-web/uri2dec/htdocs/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /home/project-web/uri2dec/htdocs/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /home/project-web/uri2dec/htdocs/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /home/project-web/uri2dec/htdocs/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /home/project-web/uri2dec/htdocs/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /home/project-web/uri2dec/htdocs/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /home/project-web/uri2dec/htdocs/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /home/project-web/uri2dec/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /home/project-web/uri2dec/htdocs/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /home/project-web/uri2dec/htdocs/wp-includes/http.php on line 61

Strict Standards: Non-static method WP_Http_ExtHTTP::test() should not be called statically, assuming $this from incompatible context in /home/project-web/uri2dec/htdocs/wp-includes/http.php on line 94

Strict Standards: Non-static method WP_Http_Curl::test() should not be called statically, assuming $this from incompatible context in /home/project-web/uri2dec/htdocs/wp-includes/http.php on line 97

Strict Standards: Non-static method WP_Http_ExtHTTP::test() should not be called statically, assuming $this from incompatible context in /home/project-web/uri2dec/htdocs/wp-includes/http.php on line 142

Strict Standards: Non-static method WP_Http_Streams::test() should not be called statically, assuming $this from incompatible context in /home/project-web/uri2dec/htdocs/wp-includes/http.php on line 145
Web call (uri2dec) open source project home page » Примеры кодирования URI десятичными цифрами

Web call (uri2dec) open source project home page

Welcome


Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 41

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 50

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 52

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 54

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 55

Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 41

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 50

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 52

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 54

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 55

Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 41

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 50

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 52

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 54

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 55

August 19, 2007

Примеры кодирования URI десятичными цифрами

Filed under: Technical notes — admin @
Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 41

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 50

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 52

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 54

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home/project-web/uri2dec/htdocs/wp-includes/functions.php on line 55
6:58 pm

Примеры кодирования URI десятичными цифрами
Статус документа

Это приложение к документу «Кодирование URI десятичными цифрами» содержит несколько примеров, поясняющих причины выбора тех или иных способов кодирования URI десятичными цифрами.

Авторские права

Copyright (C) Андрей Иванов (2006-2007). Все права зарезервированы.

Реферат

Документ обсуждает реализацию трансляции доменных имен (DNS) и универсальных идентификаторов ресурсов Интернет (URI) в последовательности десятичных цифр для обеспечения простого ввода на номеронабирателях коммуникационных устройств и декодирование этих последовательностей в URI.

Содержание
Содержание 1
1. Хэш 1
1.1 Прямой хэш 1
1.2 Инвертированный хэш 2
1.3 Укорачивание номеров 2
2. Ключ 2
3. Реализации алгоритма 3
1. Хэш
1.1 Прямой хэш
Хэш- это цифры, получаемые при нажатии клавиш номеронабирателя с соответствующими буквами.
Недостающие символы вводятся клавишей «0».

Адрес
Хэш
corwin@amber.ru
267946 0 26237 0 78
corwin@rebma.ru
267946 0 73262 0 78

corwin@amber.com
267946 0 26237 0 266
corwin@rebma.com
267946 0 73262 0 266

random@amber.com
726366 0 73262 0 266

Прямой хэш рекомендуется записывать обязательно с буквенной расшифровкой:
там, где это возможно, в виде графических изображений кнопок;
где это невозможно, указывать только адрес и не указывать хэш;
также в отдельных случаях можно указывать инвертированный хэш с ключом (п. 1.2).
1.2 Инвертированный хэш
Инвертированный хэш используется в случае, когда предпочтительнее не указывать адрес. Такими случаями могут быть:
малая информативность адреса;
отсутствие буквенных надписей на клавиатурах;
отсутствие навыка набора буквами;
Инвертированный хэш рекомендуется для записи в телефонных справочниках.
При передаче адреса абоненту рекомендуется:
при возможности передачи текста передать адрес и ключ;
при передаче голосом рекомендуется передавать инвертированный хэш и ключ.

Адрес
Инвертированный хэш (с «0» начала ключа)
corwin@amber.ru
780 262370 2679460
corwin@rebma.ru
780 732620 2679460

corwin@amber.com
2660 262370 2679460
corwin@rebma.com
2660 732620 2679460

random@amber.com
2660 262370 7263660

В таблице показано, что цифры инвертированного хеша удобно собирать в группы, оканчивающиеся “0”.
Как видно из примеров, инвертированный хеш для домена .ru начинается с 780. Для домена .com начало – 2660.
1.3 Укорачивание номеров
В справочнике номеров для одного домена первые цифры не меняются, и, если дописывается DNS суффикс в пределах сети, где распространяется справочник, то хеш можно укоротить (отбросить 780 для домена .ru и 2602370 для домена amber, например). Соответственно, укорачивается и ключ. При передаче инвертированного хэша с ключом за пределы сети нужно дополнить адрес до полного доменного имени.
2. Ключ
Ключ всегда начинается с «0» или «1». «0» используется в случае, когда указывается инвертированный хеш. Это позволяет сделать инвертированный хеш «более красивым». В случае прямого хэша это не имеет значения, поэтому для него выбрано начала ключа «1».
Ключ не содержит, кроме начала, цифр «1» и «0». Это сделано для того, чтобы ключ заменить на слово (слова), состоящее только из букв – клавиши «1» т «0» на номеронабирателе не имеют букв- эквивалентов.

Адрес
Ключ
corwin@amber.ru
1 724 5348 62623
corwin@rebma.ru
1 724 8468 62623

corwin@amber.com
1 623 3675 42422
corwin@rebma.com
1 623 5345 42422

random@amber.com
1 623 3674 63343
random@rebma.com
1 623 5344 63343

При передаче ключа абоненту рекомендуется:
при возможности передачи текста передать адрес и ключ словами-эквивалентами;
при передаче голосом рекомендуется передавать инвертированный хэш и ключ цифрами;
при записи в телефонном справочнике ключ рекомендуется записывать цифрами и, при согласии абонента, добавлять запись словами-эквивалентами.

На практике не для всех ключей можно подобрать подходящие (желаемые) слова-эквиваленты.

3. Реализации алгоритма

Алгоритм может быть реализован в коде SIP сервера, DNS сервера.

No Comments

No comments yet.

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

About Us | Site Map | Privacy Policy | Contact Us | Copyright © 2007-2011 Commandus software development group . All rights reserved. Powered by WordPress