W3C home > Mailing lists > Public > public-html@w3.org > November 2007

protocol [was: Re[2]: Feedback on the ping="" attribute (ISSUE-1) ]

From: Dmitry Turin <html60@narod.ru>
Date: Sun, 11 Nov 2007 16:22:21 +0300
Message-ID: <165505873.20071111162221@narod.ru>
To: public-html@w3.org

Julian,

>>>> I'm sure, that the best variant, when <a> behaves similar <form>.
>>>> I'm sure.
>>>> But this can require unification of HTTP for both cases.
>> JR> Uh? Are you saying you want to make GET and POST be the same?
>> Yes, definitively.
JR> Sounds good. This saves a few bytes in the request line.
I think about not ecomony, but about usability.

JR> you want to get rid of all the other HTTP methods as well? Why keep PUT and
JR> DELETE when GET is gone, after all?
+
JR> Maybe you could start with a problem statement first? What do you want
JR> to achieve by using a different protocol?
(1) First of all, many protocals make the same: e.g.
what is the _principle_ difference between HTTP, FTP, SMTP/POP3?
Don't say me about destination (for browser, for archives, for mail).
Russians name this class of sutuations as "zoo".
Is it possible to use _one_ of protocals (maybe with small additions)
instead of all other protocal? Yes, obviously.
Veriety of protocals is result of anarchy and absence of consensus of
different developers, instead of result of objective necessity.
(2) Let's imagine situation, that we have only one protocal for all cases.
At this step of analysis we have zoo once again: two tools (text and xml)
to formulate information. Already when we have zoo,
we need (i'm underlining - we need) to reduce zoo to only 1 item.

http ftp smpt/pop3
   \  |  /
     text    xml
         \  /
         tool

What is better to formulate information: text or xml?
Human consciousness needs in structurizing, and only xml gives
information in structurized type.

>> Moreover, I definitively want, that <a> and <form> send similar
>> traffic (i.e. message of identical template).
>> What's about bookmark in browsers, this is deal of browser
>> instead of address-line in them.
JR> User agents usually only bookmark the result of a GET request for a
JR> reason; repeating a POST may cause an additional action the user doesn't
JR> want (such as purchasing a book a second time).
Only sent information exists for me:
UA must remember, _what it sent by POST_ to get concrete document.

>> Moreover once again: I definitively want XML as communication protocol
>> instead of HTTP.
JR> XML is a format, not a protocol.
I want XML as format for service information. Instead of textual format.


Dmitry Turin
HTML6     (6.5.0)  http://html60.euro.ru
SQL5      (5.7.0)  http://sql50.euro.ru
Unicode7  (7.2.1)  http://unicode70.euro.ru
Computer2 (2.0.2)  http://computer20.euro.ru
Received on Monday, 12 November 2007 06:11:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:09 GMT