Re: HTTP with Simple Components: Status.Kind always File

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 20/07/2017 23:12, Felix Krause wrote:
> On 2017-07-20 20:57:35 +0000, Dmitry A. Kazakov said:
> 
>> On 2017-07-20 22:29, Simon Wright wrote:
>>>
>>> The RFC that Dmitri quotes is for URIs. You want the one that defines
>>> the HTTP protocol, currently RFC7230 - see section 3, Message Format.
>>> https://tools.ietf.org/html/rfc7230#section-3
> 
> Ah, I looked at an older RFC for HTTP 1.1; I wasn't aware there was a newer
> one. This newer one indeed defines query as part of the request target:
> 
>     https://tools.ietf.org/html/rfc7230#section-5.3
> 
>     request-target = origin-form
>                     / absolute-form
>                     / authority-form
>                     / asterisk-form
>     origin-form    = absolute-path [ "?" query ]
>>
>> So, is it OK to always recognize query part in the path. Correct?
> 
> Yes, although to avoid confusion, it may be a good idea to not name
> it „Path“. Reading the spec, „Origin“ might be more appropriate. But
> I guess that change would break backwards compatibility.

I think I will just move the Query member out of the variant choice like 
this:

    type Status_Line
         (  Kind         : Status_Line_Type;
            Path_Length  : Natural;
            Host_Length  : Natural;
            Query_Length : Natural
         )  is
    record
       Query : String (1..Query_Length);
       case Kind is
          when None =>
             null;
          when File =>
             File : String (1..Path_Length);
          when URI =>
             Scheme : Scheme_Type;
             Host   : String (1..Host_Length);
             Port   : Port_Type;
             Path   : String (1..Path_Length);
       end case;
    end record;

That should keep it backward compatible.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de