Menu
▾
▴
cpp-netlib-devel — Developers Mailing List
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(52) |
Jun
(30) |
Jul
(17) |
Aug
(9) |
Sep
(4) |
Oct
(7) |
Nov
(11) |
Dec
(19) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
(1) |
Mar
(37) |
Apr
(28) |
May
(15) |
Jun
(28) |
Jul
(7) |
Aug
(125) |
Sep
(116) |
Oct
(85) |
Nov
(14) |
Dec
(6) |
| 2009 |
Jan
(11) |
Feb
(4) |
Mar
(5) |
Apr
|
May
(9) |
Jun
(5) |
Jul
(4) |
Aug
(40) |
Sep
(1) |
Oct
(19) |
Nov
(43) |
Dec
(45) |
| 2010 |
Jan
(76) |
Feb
(95) |
Mar
(3) |
Apr
(23) |
May
(39) |
Jun
(54) |
Jul
(6) |
Aug
(13) |
Sep
(12) |
Oct
(59) |
Nov
(53) |
Dec
(43) |
| 2011 |
Jan
(43) |
Feb
(44) |
Mar
(25) |
Apr
(23) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(1) |
Nov
(2) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
|
|
From: Glyn M. <gly...@gm...> - 2008-08-11 20:11:59
|
Hi, I created a new subversion branch for documentation. I've added a few a quickbook files and an initial Jamfile (copied without shame from the boost threads library). There are some things that need to be done: 1. We're not an official part of boost, so I don't want to rely too much on this connection (I like the way asio does this). I think it would be a good idea for this project to stand up under its own scrutiny before we decide to submit it for boost review. Maybe if someone could come with a small logo, it could be good ;) 2. I've presented a pretty straightforward documentation template: - Overview - Motivation - Message - Protocols - Acknowledgements This is pretty uncontroversial and should serve us well. Adding an examples section should be trivial (once we have some examples). This will do us for starters, I think. Any comments? Or suggestions? Glyn |
|
From: Divye K. <div...@gm...> - 2008-08-11 17:27:25
|
Hi Dean, > BTW, WRT text_file_query, at this point, I'm at a loss -- maybe Python > is also the culprit here, because the response seems to be missing > exactly 4 characters (assuming we're missing the \r from the file in > the filesystem). Python might be munging the line-endings in Windows? > That's the only explanation I can think of at the moment though. > > Does this manifest when testing against IIS/Apache in Windows? Can > anybody test this? > Seems like it. I tested it with IIS7 and the error was gone. Divye -- An idealist is one who, on noticing that a rose smells better than a cabbage, concludes that it will also make better soup. H. L. Mencken (1880 - 1956) My official web site: http://people.iitr.ernet.in/shp/061305/ Webmaster: http://www.drkapoorsclinic.com Blog: http://divyekapoor.blogspot.com |
|
From: Dean M. B. <mik...@gm...> - 2008-08-11 17:17:27
|
Hi Divye, On Tue, Aug 12, 2008 at 12:25 AM, Divye Kapoor <div...@gm...> wrote: > > I was able to reproduce the issue. The error lies with a standard library > script of python not handling paths with spaces as it should. As of now, > moving the files seems to be the only option till a patch can be developed. > > Python bug ids: > 1535504 17 months ago CGIHTTPServer doesn't handle path names with embeded > space open htgoebel > 1436206 24 months ago CGIHTTPServer doesn't handle path names with embeded > space open rick-eci > 1235 7 months ago CGIHTTPRequestHandler.run_cgi() does not run on Windows if > sys.executable contains blanks > Nice one, I think working in Linux with no paths with spaces seems like the best option for me. :D BTW, WRT text_file_query, at this point, I'm at a loss -- maybe Python is also the culprit here, because the response seems to be missing exactly 4 characters (assuming we're missing the \r from the file in the filesystem). Python might be munging the line-endings in Windows? That's the only explanation I can think of at the moment though. Does this manifest when testing against IIS/Apache in Windows? Can anybody test this? -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
|
From: Dean M. B. <dmb...@fr...> - 2008-08-11 17:07:30
|
And at the risk of being chatty, I've just committed revision 56 which includes an example http client and Jamfile. :) This took me a whole of 20 minutes, more with tackling Boost.Program_Options than the actual using the HTTP client. Let me know if you think there ought to be more examples, or whether there's a better example we should be including. :D On Tue, Aug 12, 2008 at 12:18 AM, Dean Michael C. Berris <dmb...@fr...> wrote: >> -----Original Message----- >> From: cpp...@li... >> [mailto:cpp...@li...] On >> Behalf Of Dean Michael Berris >> Sent: Monday, August 11, 2008 11:41 PM >> To: C++ Networking Library Developers Mailing List >> Subject: Re: [cpp-netlib-devel] Closing of bug/patch issue >> >> On Mon, Aug 11, 2008 at 6:34 PM, Glyn Matthews >> <gly...@gm...> wrote: >> > >> > Also, I don't think its right to say we have an alpha while >> having GET >> > but not having POST, PUT and DELETE: it is simply incomplete. >> > >> >> But we not have POST, PUT, DELETE, and HEAD support. :D >> > > Of course I meant we *do* now support the following: > - GET > - HEAD > - PUT > - POST > - DELETE > > In the client implementation in branch http_integration. :D > > -- > Dean Michael Berris > Software Engineer, Friendster, Inc. > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Cpp-netlib-devel mailing list > Cpp...@li... > https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel > -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
|
From: Dean M. B. <mik...@gm...> - 2008-08-11 17:05:21
|
On Tue, Aug 12, 2008 at 12:22 AM, Glyn Matthews <gly...@gm...> wrote: > 2008/8/11 Dean Michael C. Berris <dmb...@fr...> >> >> Of course I meant we *do* now support the following: >> - GET >> - HEAD >> - PUT >> - POST >> - DELETE >> >> In the client implementation in branch http_integration. :D > > Yes, I see now :) Glad to see you making such fast progress. Me too. :D -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
|
From: Divye K. <div...@gm...> - 2008-08-11 16:25:31
|
Hi Dean, The error has something to do with the CGI script not executable > because the path has a space in it. I'm not sure if it's a Python bug > or something else, but because the HTTP server isn't able to run the > CGI script, the socket gets closed prematurely and the client gets the > error as an EOF. > I was able to reproduce the issue. The error lies with a standard library script of python not handling paths with spaces as it should. As of now, moving the files seems to be the only option till a patch can be developed. Python bug ids: 1535504 17 months ago CGIHTTPServer doesn't handle path names with embeded space <http://bugs.python.org/issue1535504> open htgoebel 1436206 24 months ago CGIHTTPServer doesn't handle path names with embeded space<http://bugs.python.org/issue1436206> open rick-eci 1235 7 months ago CGIHTTPRequestHandler.run_cgi() does not run on Windows if sys.executable contains blanks <http://bugs.python.org/issue1235> Divye -- An idealist is one who, on noticing that a rose smells better than a cabbage, concludes that it will also make better soup. H. L. Mencken (1880 - 1956) My official web site: http://people.iitr.ernet.in/shp/061305/ Webmaster: http://www.drkapoorsclinic.com Blog: http://divyekapoor.blogspot.com |
|
From: Glyn M. <gly...@gm...> - 2008-08-11 16:22:44
|
2008/8/11 Dean Michael C. Berris <dmb...@fr...> > > Of course I meant we *do* now support the following: > - GET > - HEAD > - PUT > - POST > - DELETE > > In the client implementation in branch http_integration. :D > Yes, I see now :) Glad to see you making such fast progress. G |
|
From: Dean M. C. B. <dmb...@fr...> - 2008-08-11 16:18:50
|
> -----Original Message----- > From: cpp...@li... > [mailto:cpp...@li...] On > Behalf Of Dean Michael Berris > Sent: Monday, August 11, 2008 11:41 PM > To: C++ Networking Library Developers Mailing List > Subject: Re: [cpp-netlib-devel] Closing of bug/patch issue > > On Mon, Aug 11, 2008 at 6:34 PM, Glyn Matthews > <gly...@gm...> wrote: > > > > Also, I don't think its right to say we have an alpha while > having GET > > but not having POST, PUT and DELETE: it is simply incomplete. > > > > But we not have POST, PUT, DELETE, and HEAD support. :D > Of course I meant we *do* now support the following: - GET - HEAD - PUT - POST - DELETE In the client implementation in branch http_integration. :D -- Dean Michael Berris Software Engineer, Friendster, Inc. |
|
From: Dean M. B. <mik...@gm...> - 2008-08-11 15:50:10
|
Hi Divye, On Mon, Aug 11, 2008 at 10:00 PM, Divye Kapoor <div...@gm...> wrote: >> >> I'm not sure also how to fix this, so I'm leaving it up to you. I just >> did an update now and I see that the localhost_test fails in Windows >> again, with the client throwing the same end-of-file exception. > > With the current revision (55), the client is not throwing any errors on my > machine (Vista/MSVC8) except the text_file_query showing the (apparent) file > size discrepancy. Could you post the error message? > The error has something to do with the CGI script not executable because the path has a space in it. I'm not sure if it's a Python bug or something else, but because the HTTP server isn't able to run the CGI script, the socket gets closed prematurely and the client gets the error as an EOF. Short of moving the checkout to a directory that doesn't contain spaces, I don't know what else to do to make it work. Any ideas? -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
|
From: Dean M. B. <mik...@gm...> - 2008-08-11 15:40:43
|
Hi Glyn! On Mon, Aug 11, 2008 at 6:34 PM, Glyn Matthews <gly...@gm...> wrote: > Hi, > > 2008/8/11 Dean Michael Berris <mik...@gm...> >> >> Come to think of it, unless we have either examples or documentation, >> I don't think users will even trust an Alpha version that doesn't have >> proper (or even improper) documentation. So let's hold that off until >> we get some decent documentation and examples out. :-) > > Right, that was my point. The more examples the better (they would also > reveal potential problems with the code), and it would be a good idea to > have examples to demonstrate why using this library is an improvement on, > say, the HTTP example given with Asio. > Sounds good to me. I'll try to come up with a command-line analog to wget. That should be a convincing example. ;-) > Also, I don't think its right to say we have an alpha while having GET but > not having POST, PUT and DELETE: it is simply incomplete. > But we not have POST, PUT, DELETE, and HEAD support. :D >> >> Divye/Allister, care to work on the documentation part? :-D > > I can take more responsibility for the documentation - I could always do > with improving my technical writing skills :) > Sounds good to me. :D -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
|
From: Dean M. B. <mik...@gm...> - 2008-08-11 15:38:49
|
Hi Divye, On Mon, Aug 11, 2008 at 9:39 PM, Divye Kapoor <div...@gm...> wrote: > Hi Dean, > It is possible for a POST request to send multiple body entities with > multiple content types using multipart transmission (RFC 2388) > Should we support this feature? In order to do that, we will need to analyse > the body of the message to determine suitable boundaries. > That should be pretty easy to do. I'm thinking of adding the following to support this: -.post(request, range<pair<string,string> >) Where the range contains a mapping between content-type and content. >From within, we recreate the actual request with the correct headers and the body that contains the correct format/delimiter. Or even, using Boost.Fusion: post(request, sequence) Where sequence is a Fusion sequence of STL pairs. > I have just checked in the code without unit tests -- maybe someone > who knows how to deal with the Python Server (CGI perhaps) and do > POST, PUT, and DELETE handling should take over the testing of this > code? > > There is no direct support for PUT and DELETE on the Python server > currently. I'll see how that can be implemented. > Oh. It might be something worth looking into. Thanks in advance. -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
|
From: Divye K. <div...@gm...> - 2008-08-11 14:00:53
|
Hi Dean, > > I'm not sure also how to fix this, so I'm leaving it up to you. I just > did an update now and I see that the localhost_test fails in Windows > again, with the client throwing the same end-of-file exception. > With the current revision (55), the client is not throwing any errors on my machine (Vista/MSVC8) except the text_file_query showing the (apparent) file size discrepancy. Could you post the error message? Divye -- An idealist is one who, on noticing that a rose smells better than a cabbage, concludes that it will also make better soup. H. L. Mencken (1880 - 1956) My official web site: http://people.iitr.ernet.in/shp/061305/ Webmaster: http://www.drkapoorsclinic.com Blog: http://divyekapoor.blogspot.com |
|
From: Divye K. <div...@gm...> - 2008-08-11 13:43:26
|
Hi, > Divye/Allister, care to work on the documentation part? :-D >> > > I'll have a look at Boost Book later when I get time. Some technical > writing would be interesting :-) > Maybe I'll come up with something tonight. But for now, I gotta get back > to the day job first, hehehe... > I have a some quickbook documentation. I'll try to get it going. Divye -- An idealist is one who, on noticing that a rose smells better than a cabbage, concludes that it will also make better soup. H. L. Mencken (1880 - 1956) My official web site: http://people.iitr.ernet.in/shp/061305/ Webmaster: http://www.drkapoorsclinic.com Blog: http://divyekapoor.blogspot.com |
|
From: Divye K. <div...@gm...> - 2008-08-11 13:39:37
|
Hi Dean, It is possible for a POST request to send multiple body entities with multiple content types using multipart transmission (RFC 2388) Should we support this feature? In order to do that, we will need to analyse the body of the message to determine suitable boundaries. I have just checked in the code without unit tests -- maybe someone who knows how to deal with the Python Server (CGI perhaps) and do POST, PUT, and DELETE handling should take over the testing of this code? There is no direct support for PUT and DELETE on the Python server currently. I'll see how that can be implemented. Divye -- An idealist is one who, on noticing that a rose smells better than a cabbage, concludes that it will also make better soup. H. L. Mencken (1880 - 1956) My official web site: http://people.iitr.ernet.in/shp/061305/ Webmaster: http://www.drkapoorsclinic.com Blog: http://divyekapoor.blogspot.com |
|
From: Allister L. S. <all...@gm...> - 2008-08-11 10:44:45
|
Hi, Divye/Allister, care to work on the documentation part? :-D > I'll have a look at Boost Book later when I get time. Some technical writing would be interesting :-) Maybe I'll come up with something tonight. But for now, I gotta get back to the day job first, hehehe... Cheers, Allister |
|
From: Glyn M. <gly...@gm...> - 2008-08-11 10:35:01
|
Hi, 2008/8/11 Dean Michael Berris <mik...@gm...> > > Come to think of it, unless we have either examples or documentation, > I don't think users will even trust an Alpha version that doesn't have > proper (or even improper) documentation. So let's hold that off until > we get some decent documentation and examples out. :-) > Right, that was my point. The more examples the better (they would also reveal potential problems with the code), and it would be a good idea to have examples to demonstrate why using this library is an improvement on, say, the HTTP example given with Asio. Also, I don't think its right to say we have an alpha while having GET but not having POST, PUT and DELETE: it is simply incomplete. > > Divye/Allister, care to work on the documentation part? :-D > I can take more responsibility for the documentation - I could always do with improving my technical writing skills :) Regards, Glyn |
|
From: Dean M. B. <mik...@gm...> - 2008-08-11 07:42:12
|
Hi Guys, As promised, I've further refactored the code of the HTTP Client and implemented POST, PUT, and DELETE. The API now looks like the following: client object - .put(request) : crafts a put request from the request object, without modification - .put(request, body) : crafts a copy of the request and adds a body, default content-type is 'x-application/octet-stream', content-length is body.size() - .put(request, content_type, body) : crafts a copy of the request and adds a body, content-type is content_type, content-length is body.size() - .post(request) : crafts a post request from the request object, without modification - .post(request, body) : crafts a copy of the request and adds a body, default content-type is 'x-application/octet-stream', content-length is body.size() - .post(request, content_type, body) : crafts a copy of the request and adds a body, content-type is content_type, content-length is body.size() - .delete_(request) : crafts a delete request from the request object I have just checked in the code without unit tests -- maybe someone who knows how to deal with the Python Server (CGI perhaps) and do POST, PUT, and DELETE handling should take over the testing of this code? Any takers? :D Have a good day everyone! :) -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
|
From: Dean M. B. <mik...@gm...> - 2008-08-11 06:27:54
|
Hi Guys, I've just refactored the HTTP Client's internals and implemented 'HEAD' support on top of the implementation. I'm now going to be adding POST, PUT, and DELETE support to the client. Revision 54 reflects these changes. I've also added one unit test to the localhost_test that tests HEAD support from the client. Have a good day guys! :) -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
|
From: Dean M. B. <mik...@gm...> - 2008-08-11 05:28:35
|
Hi Guys, I have the cpp-netlib http_integration branch checked out in Windows in a path that contains spaces. I keep seeing errors in the Python server saying something about having the path done wrong, or that running the CGI script from the given path is not possible (maybe because even if it is executable, the path contains spaces and is being treated as an error). Does anybody know how to fix this? The path to the source looks like this on my machine: C:\Documents and Settings\dmberris\My Documents\Source\cpp-netlib-http_integration\libs\network\test\server Short of moving the files to a path that doesn't contain spaces, any other tips/pointers for testing? -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
|
From: Dean M. B. <mik...@gm...> - 2008-08-11 01:40:34
|
On Mon, Aug 11, 2008 at 4:30 AM, Glyn Matthews <gly...@gm...> wrote: > Hello, > > 2008/8/10 Dean Michael Berris <mik...@gm...> >> >> > Also, as we are now able to support GET requests and have tests for the >> > same, I would also request that our project status be changed to "alpha" >> > from the current "planning" stage. >> > >> >> I like that. Do we agree yet Glyn? :D > > Maybe, though I'm still concerned by a lack of examples and a lack of > documentation. I'm afraid I still haven't had the time to look thoroughly > enough through the code to comment on how complete it is. Dean, if you're > comfortable with changing the status, then go ahead. I'll make an effort to > go through the latest round of changes and make comments. > Right, the hard part is still missing. :-P I can come up with simple examples, that's no problem -- it's just code anyway. ;-) But documentation is something else entirely. I don't feel comfortable writing documentation on an incomplete implementation, but if anybody wants to pick that up -- and take hints from the unit tests -- then I'm all for it. Come to think of it, unless we have either examples or documentation, I don't think users will even trust an Alpha version that doesn't have proper (or even improper) documentation. So let's hold that off until we get some decent documentation and examples out. :-) Divye/Allister, care to work on the documentation part? :-D -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
|
From: Dean M. B. <mik...@gm...> - 2008-08-11 01:35:45
|
On Mon, Aug 11, 2008 at 3:52 AM, Allister Levi Sanchez <all...@gm...> wrote: > Hi Dean, > >> I think you need to check out the source through HTTPS. Sourceforge >> requires that any writes should be done through HTTPS. >> >> svn co >> https://cpp-netlib.svn.sourceforge.net/svnroot/cpp-netlib/branches/http_integration >> > You're right :-) I managed to do a little test commit finally :-) > Cool. :-D -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
|
From: Glyn M. <gly...@gm...> - 2008-08-10 20:30:29
|
Hello, 2008/8/10 Dean Michael Berris <mik...@gm...> > > > Also, as we are now able to support GET requests and have tests for the > > same, I would also request that our project status be changed to "alpha" > > from the current "planning" stage. > > > > I like that. Do we agree yet Glyn? :D > Maybe, though I'm still concerned by a lack of examples and a lack of documentation. I'm afraid I still haven't had the time to look thoroughly enough through the code to comment on how complete it is. Dean, if you're comfortable with changing the status, then go ahead. I'll make an effort to go through the latest round of changes and make comments. Regards, Glyn |
|
From: Allister L. S. <all...@gm...> - 2008-08-10 19:52:57
|
Hi Dean, I think you need to check out the source through HTTPS. Sourceforge > requires that any writes should be done through HTTPS. > > svn co > https://cpp-netlib.svn.sourceforge.net/svnroot/cpp-netlib/branches/http_integration > > You're right :-) I managed to do a little test commit finally :-) Cheers, Allister |
|
From: Dean M. B. <mik...@gm...> - 2008-08-10 17:36:05
|
Hi Divye On Sun, Aug 10, 2008 at 7:41 PM, Divye Kapoor <div...@gm...> wrote: > Hi Dean, > Response inline. > > On Sat, Aug 9, 2008 at 7:14 PM, Dean Michael Berris <mik...@gm...> > wrote: >> >> Hi Guys, >> >> I've just checked in revision 48 which fixes the Python CGI script >> that returns incomplete headers. I had to make it print the http >> status line (which I'm not sure is required) and add the correct line >> endings to the printed header: instead of just '\n', I made it print >> "\r\n\r\n" in the end to signify that it was the last header responded >> to. > > I tested the python server using LiveHTTPHeaders addon to Firefox. The > current output from the script (after your commit) is: (for > http://localhost:8000/cgi-bin/requestinfo.py?q=1111) > > Content-type: text/plain; charset=us-ascii > > > Query string: q=1111 > GET parameters: q - ['1111'] ; > POST parameters: > > Clearly, the Content-type header is being shifted to the body. Please verify > this if you can. I have changed the print statement to use sys.stdout.write > to write unformatted strings, the print statement interprets the \n on > windows to be \r\n - thus causing this issue. Hopefully it should be fixed. > What was causing the CGI Test to fail initially? Was it the missing HTTP > header? > The CGI test caused the localhost_test to fail because without the '\r\n\r\n' combination from the HTTP response (that delimits the end of the headers section), client.get(...) throws an 'end of file' exception in boost::asio::read_until(..., "\r\n\r\n"). I added the HTTP headers thinking it must be missing or the culprit, but apparently just adding '\r\n\r\n' instead of '\n' to the Content-type header should suffice. I'm not sure if it's a bug in the Python CGI Server implementation, or has something to do with Windows now handling the end-of-line delimiters correctly. I'm not sure also how to fix this, so I'm leaving it up to you. I just did an update now and I see that the localhost_test fails in Windows again, with the client throwing the same end-of-file exception. >> >> Divye, please make sure that this is the correct way to do CGI scripts >> in Python -- I really have no idea how to do that, and I only hacked >> the script to make it not fail in just the CGI case. I haven't tried >> this in Windows yet, but I'm thinking it should be do-able. > > Hopefully this should be fixed. > I think it's fixed now too. Thanks. :) >> >> Another thing: maybe we should put the startup/shutdown of the server >> in a global fixture in the test suite for localhost_test? Has anybody >> done this with Boost.Test before? That way when we start the server, >> we should be able to stop it as well at the end of the whole test. > > That's a good idea. I just learnt about them. I'll try my hand at it. > Hope to see your check-in soon. :) BTW, I'm thinking of using fixtures in our unit tests so that we cut down on repetitive code. I'll add more tests to the message framework to show what I mean later. For the meantime, I'm going to implement the head function call to support HEAD queries from the client side. HTH -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
|
From: Dean M. B. <mik...@gm...> - 2008-08-10 16:48:38
|
Hi Divye, On Mon, Aug 11, 2008 at 12:14 AM, Divye Kapoor <div...@gm...> wrote: > Dear admins, > The sole patch entry in our database can be safely said to have been > resolved as suitable tests have been added and the code modified > accordingly. I request the admins to mark the issue closed. > > url: http://sourceforge.net/tracker/?atid=958385&group_id=196670&func=browse > Thanks. :D > Also, as we are now able to support GET requests and have tests for the > same, I would also request that our project status be changed to "alpha" > from the current "planning" stage. > I like that. Do we agree yet Glyn? :D -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |
7 messages has been excluded from this view by a project administrator.
