unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Marco Maggi" <marco.maggi-ipsu@poste.it>
To: "guile-user" <guile-user@gnu.org>
Subject: [announce] GEE/NURI version 0.4b0
Date: Sat,  8 Dec 2007 11:59:07 +0100	[thread overview]
Message-ID: <JSQ96J$1A031FB86F302B623B59714078DB98DA@poste.it> (raw)

GEE/NURI version 0.4b0 is available.

<http://gna.org/projects/gee>
<http://marcomaggi.jottit.com/gee-nuri/gee-nuri.html>
<http://www.webdav.org/neon/>

This version is tested with Guile 1.8.3.

GEE/NURI is  a C language  library extension for  Guile, the
GNU's  Ubiquitous Intelligent  Language for  Extensions.  It
implements Uniform Resource Identifier (URI) handling.

The code is built uopn  a module from Neon: a client library
for  HTTP and  WebDAV (Web-based  Distributed  Authoring and
Versioning).  Neon author is Joe Orton <joe/manyfish.co.uk>

You  can use  GEE/NURI under  the terms  of the  GNU General
Public  License version  2, or  (at your  option)  any later
version.

Neon  is distributed  under  the terms  of  the GNU  General
Public License version 2.

The module creates a custom  SMOB type to handle URI values,
and  it exports a  <nuri> GOOPS  class that  can be  used to
dispatch  methods. Unfortunately  Guile  1.8 has  no way  to
select a base <uri> class.

Example: this script:

(define-module (nuri-examples)
  #:use-module (oop goops)
  #:use-module (ice-9 format)
  #:use-module (gee net nuri-1)
  #:duplicates merge-generics)

(format #t "Escaped path: ~A~%~%"
	(nuri-path-escape "http://a.b.c/path/to&bar"))

(define uri (make-nuri

"http://marco:maggi@www.home.it:8080/woppa/wippa.txt?query=123#fragment"))

(format #t "URI: ~A~%" (nuri-uri->string uri))
(format #t "Scheme:~/~/'~A'~%" (scheme uri))
(format #t "Host:~/~/'~A'~%" (host uri))
(format #t "Userinfo:~/'~A'~%" (userinfo uri))
(format #t "Port:~/~/'~A'~%" (port uri))
(format #t "Path:~/~/'~A'~%" (path uri))
(format #t "Query:~/~/'~A'~%" (query uri))
(format #t "Fragment:~/'~A'~%" (fragment uri))

outputs:

Escaped path: http%3a//a.b.c/path/to%26bar

URI:
http://marco:maggi@www.home.it:8080/woppa/wippa.txt?query=123#fragment
Scheme:		'http'
Host:		'www.home.it'
Userinfo:	'marco:maggi'
Port:		'8080'
Path:		'/woppa/wippa.txt'
Query:		'query=123'
Fragment:	'fragment'


I am  always available to accept  new manipulation functions
for <nuri> SMOBs.


  <DT><B><A HREF="http://gna.org/projects/gee">GEE/NURI</A></B>
  <DD><TABLE>
  <TR><TD><I>description</I></TD>
  <TD>Uniform Resource Identifier (URI) handling</TD></TR>
  <TR><TD><I>license</I></TD>
  <TD>GNU General Public License version 2, or (at your
      option) any later version.</TD></TR>
  <TR><TD><I>requires</I></TD>
  <TD>Guile 1.8</TD></TR>
  </TABLE><P>

It should go into the Networking section.

--
Marco Maggi

"Now feel the funk blast!"
Rage Against the Machine - "Calm like a bomb"




_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


             reply	other threads:[~2007-12-08 10:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08 10:59 Marco Maggi [this message]
2007-12-08 15:27 ` [announce] GEE/NURI version 0.4b0 Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to='JSQ96J$1A031FB86F302B623B59714078DB98DA@poste.it' \
    --to=marco.maggi-ipsu@poste.it \
    --cc=guile-user@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).