From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <oliver@first.in-berlin.de>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104])
	by sympa.inria.fr (Postfix) with ESMTPS id 48E427EEB6
	for <caml-list@sympa.inria.fr>; Tue,  5 Feb 2013 11:48:08 +0100 (CET)
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  oliver@first.in-berlin.de) identity=pra;
  client-ip=192.109.42.8;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="oliver@first.in-berlin.de";
  x-sender="oliver@first.in-berlin.de";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  oliver@first.in-berlin.de) identity=mailfrom;
  client-ip=192.109.42.8;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="oliver@first.in-berlin.de";
  x-sender="oliver@first.in-berlin.de";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@einhorn.in-berlin.de) identity=helo;
  client-ip=192.109.42.8;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="oliver@first.in-berlin.de";
  x-sender="postmaster@einhorn.in-berlin.de";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoCAObhEFHAbSoIe2dsb2JhbABFv10WDgEBFiYEI4IgAQU6TwtGVwaIJASrTJAkkHlhA5YhhXCNXg
X-IPAS-Result: AgoCAObhEFHAbSoIe2dsb2JhbABFv10WDgEBFiYEI4IgAQU6TwtGVwaIJASrTJAkkHlhA5YhhXCNXg
X-IronPort-AV: E=Sophos;i="4.84,602,1355094000"; 
   d="scan'208";a="1108060"
Received: from einhorn.in-berlin.de ([192.109.42.8])
  by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Feb 2013 11:42:50 +0100
X-Envelope-From: oliver@first.in-berlin.de
Received: from [100.96.64.110] (tmo-110-238.customers.d1-online.com [80.187.110.238])
	(authenticated bits=0)
	by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id r15Am39a017825
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Tue, 5 Feb 2013 11:48:06 +0100
References: <20130204233749.GA2065@siouxsie>
In-Reply-To: <20130204233749.GA2065@siouxsie>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <9F09DC84-A30E-43FA-BE66-F6E9BE5C7F22@first.in-berlin.de>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (10B141)
From: Oliver Bandel <oliver@first.in-berlin.de>
Date: Tue, 5 Feb 2013 11:48:04 +0100
To: "caml-list@inria.fr" <caml-list@inria.fr>
X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8
Subject: Re: [Caml-list] OCaml-Curl - good docs?

To be more precise in the question I had with ocaml-curl...
the cookies will be given back as strings only.
So my question I had was... at which position is which attribute.

I found out that ocaml-curl can be set to be verbose.
The the information, which then will be printed shows,that the cookie attri=
butes are known.
e.g. name and expiration and so on.

But the return value is just a string.
A record with accordingly named fields would make more sense.

I don't know, where the verbosity was coming from,
curllib or ocaml-curl.
At least somewhere the fields are known by name.
And then this information is lost somewehere.

Either curl gives it back unnamed to the caller (and the attributes are som=
ewhere deep in the lib), or ocaml-curl does give it back unnamed.
If the latter, IMHO  the Library should become enhanced.
If it is a curllib problem, at that point things should be enhanced, and oc=
aml-curl then too.

Independent of this IMHO a better layout at the curllib pages could enhance=
 usability=20
a lot (e.g. menues that are exchanged, instead of displaying the menue hier=
archy the whole time,
do not help to get an overview).

Ciao,
   Oliver=