Thread: [cpp-netlib-devel] Adding files to the sandbox

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Guys,

I have something I want to put in the sandbox, how do I add them to the
repository?

Regards,
Glyn

Hi Glyn!

You should be able to check out the sandbox, then using your
subversion client add the files to your local working copy, then do a
commit. I'll be online through Yahoo Messenger and Google Talk later,
I can try and help you out if you're having trouble with the sandbox
and subversion.

Hope this helps!

On 6/3/07, Glyn Matthews <gly...@gm...> wrote:
> Guys,
>
> I have something I want to put in the sandbox, how do I add them to the
> repository?
>
> Regards,
> Glyn
>

-- 
Dean Michael C. Berris
http://cplusplus-soup.blogspot.com/
mikhailberis AT gmail DOT com
+63 928 7291459

OK thanks Dean, I was trying to use SVN import.

I added some stuff to parse URIs using boost spirit, it doesn't quite work
(there is something wrong with the way I've done the domain names), but I
hope I can open it up comments and improvements.

The list has been rather quiet in the last week.  Has anyone made any
progress?
G

On 03/06/07, Dean Michael Berris <mik...@gm...> wrote:
>
> Hi Glyn!
>
> You should be able to check out the sandbox, then using your
> subversion client add the files to your local working copy, then do a
> commit. I'll be online through Yahoo Messenger and Google Talk later,
> I can try and help you out if you're having trouble with the sandbox
> and subversion.
>
> Hope this helps!
>
>
> On 6/3/07, Glyn Matthews <gly...@gm...> wrote:
> > Guys,
> >
> > I have something I want to put in the sandbox, how do I add them to the
> > repository?
> >
> > Regards,
> > Glyn
> >
>
>
> --
> Dean Michael C. Berris
> http://cplusplus-soup.blogspot.com/
> mikhailberis AT gmail DOT com
> +63 928 7291459
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Cpp-netlib-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel
>

Hi Glyn!

On 6/3/07, Glyn Matthews <gly...@gm...> wrote:
> OK thanks Dean, I was trying to use SVN import.
>
> I added some stuff to parse URIs using boost spirit, it doesn't quite work (there is something wrong with the way I've done the domain names), but I hope I can open it up comments and improvements.
>

Sounds like something worth looking at. :) Thanks Glyn!

> The list has been rather quiet in the last week.  Has anyone made any progress?

I personally haven't -- the work at Friendster had been keeping me
busy for the past week, not enough time to do any sort of forward
progress...

Look for a bit more documentation though, I've been concentrating a
lot in distilling the thoughts and actually coming out with a
clear-cut document saying what I'd like the networking library to
contain (of course, which also takes into account the suggestions and
'want to haves' we've pretty much listed down in a different thread).

If the pace is not fast enough, I'd welcome any sort of help in doing
that -- we have the Sourceforge Wiki available, and I have enabled
everyone to be able to write there.

I shold be getting back into implementing the transformation layers of
the message class, and hopefully have a (very) simple HTTP client and
asynchronous resolver wrapping the Boost.Asio resolver class and some
non-trivial examples. Hopefully the projects I'm part of in Friendster
start getting finished and so I can spend more time open sourcing the
memcache client library we've developed in house and this networking
library. :)

Until then, I'd appreciate all the help and feedback from everyone.

So if you have thoughts, and questions, I'd love to hear from you!

Thanks again Glyn. :)

-- 
Dean Michael C. Berris
http://cplusplus-soup.blogspot.com/
mikhailberis AT gmail DOT com
+63 928 7291459

Hi Glyn,

 > The list has been rather quiet in the last week. Has anyone
 > made any progress?

Well, I find it hard to contribute because I don't know into
which direction this project is headed. That makes it difficult
to tell what exactly would constitute progress. I'll remain an
interested observer until I have a better understanding of
cpp-netlib's scope and goals.

Best regards,
Peter

On 03 Jun 2007 18:17:47 +0200, Peter Simons <si...@cr...> wrote:
> Hi Glyn,
>
>  > The list has been rather quiet in the last week. Has anyone
>  > made any progress?
>
> Well, I find it hard to contribute because I don't know into
> which direction this project is headed. That makes it difficult
> to tell what exactly would constitute progress. I'll remain an
> interested observer until I have a better understanding of
> cpp-netlib's scope and goals.
>

Hi Peter!

I understand. Let me deliver the intended direction, scope, and goals
in a document (currently still under development) and hope to hear
what you think. I certainly value the insights everybody have been
sharing into what the networking library should and should not
contain, and how and how not things should be done.

I admit, I'm not very good at writing documentation -- but I do think
a lot in terms of actual implementation. I find it hard to write down
directions, goals, and scope but I would gladly implement it in C++
then have people try and use it. Case in point are the other libs I've
developed (the BDD interface and Runtime Dynamic Dispatcher) where the
implementations are code complete, but lacking in documentation -- it
seems that someone always needs to ask a question first before I be
able to explain what it does or doesn't do.

So consider this a call for help in that regard. :D

(If only blogging about it would be good enough... I would have done
that a long time ago) ;-)

> Best regards,
> Peter
>

Thanks Peter!

-- 
Dean Michael C. Berris
http://cplusplus-soup.blogspot.com/
mikhailberis AT gmail DOT com
+63 928 7291459

On 6/3/07, Glyn Matthews <gly...@gm...> wrote:
>
> OK thanks Dean, I was trying to use SVN import.
>
> I added some stuff to parse URIs using boost spirit, it doesn't quite work
> (there is something wrong with the way I've done the domain names), but I
> hope I can open it up comments and improvements.
>

Hi Glyn,

Peter's server daemon code already has a complete URI parser (I think!).

Given that URI parsing is the most common operation, I wonder whether there
would be a performance advantage by parsing the URI via a state machine vs
spirit

regards
jose

Hi Jose,

you are right, there is a spirit-based URI parser in mini-httpd.
Unfortunately, it is incomplete insofar as that it understands
HTTP URLs only and doesn't recognize literal IPv6 host names. In
addition, the code is a bit messy because it was written several
years ago, at a time where Spirit didn't have the sophisticated
actor infrastructure it has these days.

In my experience, the greatest challenge when parsing an URI is
not the parser, it is the resulting data structure. The URI class
mini-httpd uses in fine for mini-httpd, but it certainly is far
from generic.

RFC 2396 comes with a state-machine for parsing URIs, by the way,
and it's pretty wild:

 |    ^(([^:/?#]+):)?(//([^/?#]*))?([^?#]*)(\?([^#]*))?(#(.*))?
 |     12            3  4          5       6  7        8 9

The relevant sub-match states are:

 |    scheme    = $2
 |    authority = $4
 |    path      = $5
 |    query     = $7
 |    fragment  = $9

In terms of performance, I doubt that there is much of a
difference between Spirit and Boost.Regex in this context. The
main difference is that Boost.Regex must be linked whereas Spirit
is a header-only library. That may or may not matter to our
users; it's hard to tell.

One disadvantage of Spirit is that compile-time goes through the
roof even for trivial grammars. Another problem is that Spirit
relies one rather sophisticated magic to be thread-safe. Compiled
regular expressions, however, are immutable and can be used by
any number of threads concurrently without synchronization.

A hand-written parser might be slightly faster than either Spirit
or Boost.Regex. It's definitely harder to get right, though. :-)

Best regards,
Peter

Hi Peter,

Thanks for the detailed answer.

I think a hand-written parser may be a good idea, maybe just for http uris:

user:password@host:port/file

so that the the typical (host, file) pair needed for HTTP requests can be
obtained as
quickly as possible. Additional parsing of the file segment can be provided
when needed (e.g. for server apps).

What do you think ?

regards
Jose

On 03 Jun 2007 23:17:55 +0200, Peter Simons <si...@cr...> wrote:
>
> Hi Jose,
>
> you are right, there is a spirit-based URI parser in mini-httpd.
> Unfortunately, it is incomplete insofar as that it understands
> HTTP URLs only and doesn't recognize literal IPv6 host names. In
> addition, the code is a bit messy because it was written several
> years ago, at a time where Spirit didn't have the sophisticated
> actor infrastructure it has these days.
>
> In my experience, the greatest challenge when parsing an URI is
> not the parser, it is the resulting data structure. The URI class
> mini-httpd uses in fine for mini-httpd, but it certainly is far
> from generic.
>
> RFC 2396 comes with a state-machine for parsing URIs, by the way,
> and it's pretty wild:
>
> |    ^(([^:/?#]+):)?(//([^/?#]*))?([^?#]*)(\?([^#]*))?(#(.*))?
> |     12            3  4          5       6  7        8 9
>
> The relevant sub-match states are:
>
> |    scheme    = $2
> |    authority = $4
> |    path      = $5
> |    query     = $7
> |    fragment  = $9
>
> In terms of performance, I doubt that there is much of a
> difference between Spirit and Boost.Regex in this context. The
> main difference is that Boost.Regex must be linked whereas Spirit
> is a header-only library. That may or may not matter to our
> users; it's hard to tell.
>
> One disadvantage of Spirit is that compile-time goes through the
> roof even for trivial grammars. Another problem is that Spirit
> relies one rather sophisticated magic to be thread-safe. Compiled
> regular expressions, however, are immutable and can be used by
> any number of threads concurrently without synchronization.
>
> A hand-written parser might be slightly faster than either Spirit
> or Boost.Regex. It's definitely harder to get right, though. :-)
>
> Best regards,
> Peter
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Cpp-netlib-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel
>