caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Oliver Bandel <oliver@first.in-berlin.de>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml-Curl - good docs?
Date: Tue, 5 Feb 2013 11:48:04 +0100	[thread overview]
Message-ID: <9F09DC84-A30E-43FA-BE66-F6E9BE5C7F22@first.in-berlin.de> (raw)
In-Reply-To: <20130204233749.GA2065@siouxsie>

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 attributes 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 somewhere 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 ocaml-curl then too.

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

Ciao,
   Oliver

      reply	other threads:[~2013-02-05 10:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 23:37 oliver
2013-02-05 10:48 ` Oliver Bandel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9F09DC84-A30E-43FA-BE66-F6E9BE5C7F22@first.in-berlin.de \
    --to=oliver@first.in-berlin.de \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).