Menu
▾
▴
naviserver-devel — Developer discussion
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
(53) |
Mar
(62) |
Apr
(88) |
May
(55) |
Jun
(204) |
Jul
(52) |
Aug
|
Sep
(1) |
Oct
(94) |
Nov
(15) |
Dec
(68) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(130) |
Feb
(105) |
Mar
(34) |
Apr
(61) |
May
(41) |
Jun
(92) |
Jul
(176) |
Aug
(102) |
Sep
(247) |
Oct
(69) |
Nov
(32) |
Dec
(140) |
| 2007 |
Jan
(58) |
Feb
(51) |
Mar
(11) |
Apr
(20) |
May
(34) |
Jun
(37) |
Jul
(18) |
Aug
(60) |
Sep
(41) |
Oct
(105) |
Nov
(19) |
Dec
(14) |
| 2008 |
Jan
(3) |
Feb
|
Mar
(7) |
Apr
(5) |
May
(123) |
Jun
(5) |
Jul
(1) |
Aug
(29) |
Sep
(15) |
Oct
(21) |
Nov
(51) |
Dec
(3) |
| 2009 |
Jan
|
Feb
(36) |
Mar
(29) |
Apr
|
May
|
Jun
(7) |
Jul
(4) |
Aug
|
Sep
(4) |
Oct
|
Nov
(13) |
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
(9) |
Apr
(11) |
May
(16) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
(7) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(92) |
Nov
(28) |
Dec
(16) |
| 2013 |
Jan
(9) |
Feb
(2) |
Mar
|
Apr
(4) |
May
(4) |
Jun
(6) |
Jul
(14) |
Aug
(12) |
Sep
(4) |
Oct
(13) |
Nov
(1) |
Dec
(6) |
| 2014 |
Jan
(23) |
Feb
(19) |
Mar
(10) |
Apr
(14) |
May
(11) |
Jun
(6) |
Jul
(11) |
Aug
(15) |
Sep
(41) |
Oct
(95) |
Nov
(23) |
Dec
(11) |
| 2015 |
Jan
(3) |
Feb
(9) |
Mar
(19) |
Apr
(3) |
May
(1) |
Jun
(3) |
Jul
(11) |
Aug
(1) |
Sep
(15) |
Oct
(5) |
Nov
(2) |
Dec
|
| 2016 |
Jan
(7) |
Feb
(11) |
Mar
(8) |
Apr
(1) |
May
(3) |
Jun
(17) |
Jul
(12) |
Aug
(3) |
Sep
(5) |
Oct
(19) |
Nov
(12) |
Dec
(6) |
| 2017 |
Jan
(30) |
Feb
(23) |
Mar
(12) |
Apr
(32) |
May
(27) |
Jun
(7) |
Jul
(13) |
Aug
(16) |
Sep
(6) |
Oct
(11) |
Nov
|
Dec
(12) |
| 2018 |
Jan
(1) |
Feb
(5) |
Mar
(6) |
Apr
(7) |
May
(23) |
Jun
(3) |
Jul
(2) |
Aug
(1) |
Sep
(6) |
Oct
(6) |
Nov
(10) |
Dec
(3) |
| 2019 |
Jan
(26) |
Feb
(15) |
Mar
(9) |
Apr
|
May
(8) |
Jun
(14) |
Jul
(10) |
Aug
(10) |
Sep
(4) |
Oct
(2) |
Nov
(20) |
Dec
(10) |
| 2020 |
Jan
(10) |
Feb
(14) |
Mar
(29) |
Apr
(11) |
May
(25) |
Jun
(21) |
Jul
(23) |
Aug
(12) |
Sep
(19) |
Oct
(6) |
Nov
(8) |
Dec
(12) |
| 2021 |
Jan
(29) |
Feb
(9) |
Mar
(8) |
Apr
(8) |
May
(2) |
Jun
(2) |
Jul
(9) |
Aug
(9) |
Sep
(3) |
Oct
(4) |
Nov
(12) |
Dec
(13) |
| 2022 |
Jan
(4) |
Feb
|
Mar
(4) |
Apr
(12) |
May
(15) |
Jun
(7) |
Jul
(10) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(8) |
Dec
|
| 2023 |
Jan
(15) |
Feb
|
Mar
(23) |
Apr
(1) |
May
(2) |
Jun
(10) |
Jul
|
Aug
(22) |
Sep
(19) |
Oct
(2) |
Nov
(20) |
Dec
|
| 2024 |
Jan
(1) |
Feb
|
Mar
(16) |
Apr
(15) |
May
(6) |
Jun
(4) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(13) |
Nov
(18) |
Dec
(6) |
| 2025 |
Jan
(12) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(11) |
Jun
(5) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Zoran V. <zv...@ar...> - 2005-02-15 17:18:20
|
On Tuesday 15 February 2005 18:11, Bernd Eidenschink wrote: > > for you to check. If there are any things you need to fix, > > tell now, so we can proceed. > > downloaded it and compiled it against tcl 4.8.9. works. > minor minor thing: the README speaks of "AOLserver 4.0.8" in the > first paragraph. > Oh yes. The README (as with the most accompanying doc/test things) must be changed accordingly. This is a work in progress :-) I will try to concentrate on first-things-first: doc. Stephen and Vlad can try figure out how to plugin the multi-protocol stuff and we all should review and bless RFE's; bugs we do not have, yet :-) Cheers, Zoran |
|
From: Bernd E. <eid...@we...> - 2005-02-15 17:06:18
|
> for you to check. If there are any things you need to fix, > tell now, so we can proceed. downloaded it and compiled it against tcl 4.8.9. works. minor minor thing: the README speaks of "AOLserver 4.0.8" in the first paragraph. |
|
From: Vlad S. <vl...@cr...> - 2005-02-15 16:39:13
|
Looks good Zoran Vasiljevic wrote: > On Saturday 12 February 2005 17:53, Zoran Vasiljevic wrote: > >>This is the current layout: >> >>aclocal.m4 configure.in include install-sh nscgi nsdb nspd nsssl sample-config.tcl tests >>ChangeLog CVS index.html license.terms nscp nsext nsperm nsthread tcl win32 >>configure doc ini2tcl.tcl Makefile nsd nslog nssock README tcl2ini.tcl >> > > > I have done the initial cleanup: > > o. removed all those silly *.html pages from various places > containing nothing but (mostly) junk; this info should > go into the docs finally > > o. removed traces of nsssl module > > o. removed most of the tests and kept only those written > lately which utilize tcltest environment > > o. reset ChangeLog > > o. removed ini2tcl.tcl and tcl2ini.tcl files > > I have put the tarball on the: > > http://www.archiware.com/www/downloads/aolserver_v40_r10.tar.gz > > for you to check. If there are any things you need to fix, > tell now, so we can proceed. > > Cheers > Zoran > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |
|
From: Zoran V. <zv...@ar...> - 2005-02-15 16:29:37
|
On Saturday 12 February 2005 17:53, Zoran Vasiljevic wrote:
>
> This is the current layout:
>
> aclocal.m4 configure.in include install-sh nscgi nsdb nspd nsssl sample-config.tcl tests
> ChangeLog CVS index.html license.terms nscp nsext nsperm nsthread tcl win32
> configure doc ini2tcl.tcl Makefile nsd nslog nssock README tcl2ini.tcl
>
I have done the initial cleanup:
o. removed all those silly *.html pages from various places
containing nothing but (mostly) junk; this info should
go into the docs finally
o. removed traces of nsssl module
o. removed most of the tests and kept only those written
lately which utilize tcltest environment
o. reset ChangeLog
o. removed ini2tcl.tcl and tcl2ini.tcl files
I have put the tarball on the:
http://www.archiware.com/www/downloads/aolserver_v40_r10.tar.gz
for you to check. If there are any things you need to fix,
tell now, so we can proceed.
Cheers
Zoran
|
|
From: Stephen D. <sd...@gm...> - 2005-02-15 08:22:05
|
Sorry, the full history thing is a no-go, I misunderstood what you said in your earlier email... You wouldn't be able to extract only the 4.0 branch from the cvs backup anyway. 4.0.10 is good. I just added a switch parsing RFE. Extracted from my repo and diffed against 4.0.10, but untested. Shouldn't be too much wrong. Find your gnarliest switch parsing code and give it a try... On Tue, 15 Feb 2005 06:58:38 +0100, Zoran Vasiljevic <zv...@ar...> wrote: > On Tuesday 15 February 2005 04:01, Vlad Seryakov wrote: > > Hey guys, > > > > I got the cable working again, i am alive. > > > > So what is the current status? > > I know everybody is busy, just to be on the same page? > > Do we have CVS operational yet? > > > > We don't. I'm pretty swamped with one support issue since > monday so I was unable to get anything in. > I have checked out the 4.0.10 clean and wanted to prune > some things (as said in my last mail) didn't get to it > since. I suppose if everybody is fine with clean 4.0.10 > import I can do this today or tomorrow. > Stephen mentioned importing the whole cvs together with > history but this is more work (I've never done it before). > OTOH, importing the clean state isn't hence I think I can > push it somewhere in between. > Which way would be more acceptable for you: clean import > or cvs-history import? > > For the cvs history import, I assume I should backup the > entire CVS from the aolserver project (I think I can do > that - I'm one of the admins there). I would still have > to examine how this goes, really. |
|
From: Zoran V. <zv...@ar...> - 2005-02-15 06:02:05
|
On Tuesday 15 February 2005 04:01, Vlad Seryakov wrote: > Hey guys, > > I got the cable working again, i am alive. > > So what is the current status? > I know everybody is busy, just to be on the same page? > Do we have CVS operational yet? > We don't. I'm pretty swamped with one support issue since monday so I was unable to get anything in. I have checked out the 4.0.10 clean and wanted to prune some things (as said in my last mail) didn't get to it since. I suppose if everybody is fine with clean 4.0.10 import I can do this today or tomorrow. Stephen mentioned importing the whole cvs together with history but this is more work (I've never done it before). OTOH, importing the clean state isn't hence I think I can push it somewhere in between. Which way would be more acceptable for you: clean import or cvs-history import? For the cvs history import, I assume I should backup the entire CVS from the aolserver project (I think I can do that - I'm one of the admins there). I would still have to examine how this goes, really. > > -- > Vlad Seryakov > 571 262-8608 office > vl...@cr... > http://www.crystalballinc.com/vlad/ > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > -- With kind regards, Mit besten Gruessen, Meilleures Salutations, ___________________________________________ Zoran Vasiljevic, Vice President, CTO E-mail: mailto:zv...@ar... Web: http://www.archiware.com Phone: +49 89 319 084 98 Fax: +49 89 319 084 99 S-mail: ArchiWare(R) GmbH Gutenbergstr. 3 D-85716 Munich, Germany ___________________________________________ PresSTORE(R) - Backup Synchronize Archive |
|
From: Vlad S. <vl...@cr...> - 2005-02-15 03:03:01
|
Hey guys, I got the cable working again, i am alive. So what is the current status? I know everybody is busy, just to be on the same page? Do we have CVS operational yet? -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |
|
From: Zoran V. <zv...@ar...> - 2005-02-14 06:47:09
|
On Saturday 12 February 2005 21:41, Stephen Deasey wrote: > On Sat, 12 Feb 2005 14:56:34 +0100, Zoran Vasiljevic <zv...@ar...> wrote: > > > > Regarding CVS import: should I import the 4.0.10 state? > > > You mean take the cvs backup tarball from AOLserver cvs, rather than > start from an export of 4.0.10? It would be nice I guess to have all > that history. But can you do that without also pulling in 4.1-HEAD? What I actually ment was importing 4.0.10 clean, w/o cvs history. Even reset ChangeLog. > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > -- With kind regards, Mit besten Gruessen, Meilleures Salutations, ___________________________________________ Zoran Vasiljevic, Vice President, CTO E-mail: mailto:zv...@ar... Web: http://www.archiware.com Phone: +49 89 319 084 98 Fax: +49 89 319 084 99 S-mail: ArchiWare(R) GmbH Gutenbergstr. 3 D-85716 Munich, Germany ___________________________________________ PresSTORE(R) - Backup Synchronize Archive |
|
From: Stephen D. <sd...@gm...> - 2005-02-12 20:41:46
|
On Sat, 12 Feb 2005 14:56:34 +0100, Zoran Vasiljevic <zv...@ar...> wrote: > > Regarding CVS import: should I import the 4.0.10 state? You mean take the cvs backup tarball from AOLserver cvs, rather than start from an export of 4.0.10? It would be nice I guess to have all that history. But can you do that without also pulling in 4.1-HEAD? |
|
From: Stephen D. <sd...@gm...> - 2005-02-12 20:25:05
|
OK. You can't use the words 'my' or 'open'. That's the law :-) Clearly, given it's age and namespace, the project must be called Naviserver, Netscape or NeXTSTEP... :-) On Sat, 12 Feb 2005 17:14:02 +0100, Zoran Vasiljevic <zv...@ar...> wrote: > On Saturday 12 February 2005 17:08, vl...@cr... wrote: > > mynsd > > > > naviweb > > nsdserver > > nsweb > > navicore > > navisystem > > > > -------- Original Message -------- > > To: nav...@li... > > From: Zoran Vasiljevic <zv...@ar...> > > Subject: [naviserver-devel] name ideas > > > > > > Personally, I have no problem with naviserver but > > just in case we'd need to change it, what about: > > > > naviengine > > navihttpd > > neohttpd > > > > (to be continued...) > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > _______________________________________________ > > naviserver-devel mailing list > > nav...@li... > > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > > > > > > > > > > -- > With kind regards, > Mit besten Gruessen, > Meilleures Salutations, > ___________________________________________ > Zoran Vasiljevic, Vice President, CTO > > E-mail: mailto:zv...@ar... > Web: http://www.archiware.com > Phone: +49 89 319 084 98 > Fax: +49 89 319 084 99 > S-mail: ArchiWare(R) GmbH > Gutenbergstr. 3 > D-85716 Munich, Germany > ___________________________________________ > PresSTORE(R) - Backup Synchronize Archive > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > |
|
From: Stephen D. <sd...@gm...> - 2005-02-12 20:19:16
|
Are these changes/deletions best done before initial import? If anything needs to be moved, we should probably do that early on to preserve as much history as possible. On Sat, 12 Feb 2005 17:53:30 +0100, Zoran Vasiljevic <zv...@ar...> wrote: > > This is the current layout: > > aclocal.m4 configure.in include install-sh nscgi nsdb nspd nsssl sample-config.tcl tests > ChangeLog CVS index.html license.terms nscp nsext nsperm nsthread tcl win32 > configure doc ini2tcl.tcl Makefile nsd nslog nssock README tcl2ini.tcl > > a) > I would scrap entirely: > ini2tcl.tcl > tcl2ini.tcl > index.html Yeah, I think these have past their sell-by date. > b) > What about nsssl? I never used it. Is this something which is > internationaly viable or is it US-only? Do people normally use > the nsopenssl instead of this beast? What do you think? > I see some ugly export notices there which are pretty old and > obsolete. I've never used this. Some modules are obviously core to a webserver and should be shipped by default: nslog, nscgi etc. I'm not sure whether it's best to remove this or to swap it with nsopenssl. I guess we can alway add nsopenssl to core later when it stabilises. > c) > I will leave the license info in the files as-is. > Also, license.terms will stay the same (MPL). Yup. > d) > Tests are pretty neglected, Tests require you to poke the > server from the browser which is partly ok, but I'd rather > do "make test" instead. > I could imagine writing test suite with the Tcl test > environment which can then be called out of the makefile > after the compilation. It might be that something should > be extra written/compiled in order to test code requiring > browser access or such. Haven't thought that much about > it yet. Only noting that the current test suite is ridiculous. > I could imagine dropping this part (except the top-level dir) > entirely and writing new test suite from scratch. I don't understand why the Tcl test stuff isn't used. It does seem to insist on writing to stdout which sucks if you're testing from a web page, but I'm sure that's not insurmountable and as you say, ideally you want to 'make test' anyway. Dump this stuff.. > e) Docs are useless. I will however keep the files and > will replace the content over the time as I convert stuff > found on aolserver site and on wiki into a manageable > sources in doctools. Groovy. > So far for now. More might come... If you have any other > idea or suggestion, please step out before I commit all. How about a top level cvs structure of: /server /modules /website I'm interested in moving more towards a standard autotools setup to make RPM/Deb building easier. There's all kinds of things that *could* be done, like moving all the sources into a top level ./src directory, using libtool to explicitly build a libnsd, and so on, but that's probably too much to tackle right now. What you've mentioned above looks like a good start. |
|
From: <vl...@cr...> - 2005-02-12 17:06:14
|
a) agree b) let's get rid of it c) agree d) agree d) agree -------- Original Message -------- To: nav...@li... From: Zoran Vasiljevic <zv...@ar...> Subject: [naviserver-devel] cleanup before first import (questions) This is the current layout: aclocal.m4 configure.in include install-sh nscgi nsdb nspd nsssl sample-config.tcl tests ChangeLog CVS index.html license.terms nscp nsext nsperm nsthread tcl win32 configure doc ini2tcl.tcl Makefile nsd nslog nssock README tcl2ini.tcl a) I would scrap entirely: ini2tcl.tcl tcl2ini.tcl index.html b) What about nsssl? I never used it. Is this something which is internationaly viable or is it US-only? Do people normally use the nsopenssl instead of this beast? What do you think? I see some ugly export notices there which are pretty old and obsolete. c) I will leave the license info in the files as-is. Also, license.terms will stay the same (MPL). d) Tests are pretty neglected, Tests require you to poke the server from the browser which is partly ok, but I'd rather do "make test" instead. I could imagine writing test suite with the Tcl test environment which can then be called out of the makefile after the compilation. It might be that something should be extra written/compiled in order to test code requiring browser access or such. Haven't thought that much about it yet. Only noting that the current test suite is ridiculous. I could imagine dropping this part (except the top-level dir) entirely and writing new test suite from scratch. e) Docs are useless. I will however keep the files and will replace the content over the time as I convert stuff found on aolserver site and on wiki into a manageable sources in doctools. So far for now. More might come... If you have any other idea or suggestion, please step out before I commit all. -- With kind regards, Mit besten Gruessen, Meilleures Salutations, ___________________________________________ Zoran Vasiljevic, Vice President, CTO E-mail: mailto:zv...@ar... Web: http://www.archiware.com Phone: +49 89 319 084 98 Fax: +49 89 319 084 99 S-mail: ArchiWare(R) GmbH Gutenbergstr. 3 D-85716 Munich, Germany ___________________________________________ PresSTORE(R) - Backup Synchronize Archive ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ naviserver-devel mailing list nav...@li... https://lists.sourceforge.net/lists/listinfo/naviserver-devel |
|
From: Zoran V. <zv...@ar...> - 2005-02-12 16:56:47
|
This is the current layout: aclocal.m4 configure.in include install-sh nscgi nsdb nspd nsssl sample-config.tcl tests ChangeLog CVS index.html license.terms nscp nsext nsperm nsthread tcl win32 configure doc ini2tcl.tcl Makefile nsd nslog nssock README tcl2ini.tcl a) I would scrap entirely: ini2tcl.tcl tcl2ini.tcl index.html b) What about nsssl? I never used it. Is this something which is internationaly viable or is it US-only? Do people normally use the nsopenssl instead of this beast? What do you think? I see some ugly export notices there which are pretty old and obsolete. c) I will leave the license info in the files as-is. Also, license.terms will stay the same (MPL). d) Tests are pretty neglected, Tests require you to poke the server from the browser which is partly ok, but I'd rather do "make test" instead. I could imagine writing test suite with the Tcl test environment which can then be called out of the makefile after the compilation. It might be that something should be extra written/compiled in order to test code requiring browser access or such. Haven't thought that much about it yet. Only noting that the current test suite is ridiculous. I could imagine dropping this part (except the top-level dir) entirely and writing new test suite from scratch. e) Docs are useless. I will however keep the files and will replace the content over the time as I convert stuff found on aolserver site and on wiki into a manageable sources in doctools. So far for now. More might come... If you have any other idea or suggestion, please step out before I commit all. -- With kind regards, Mit besten Gruessen, Meilleures Salutations, ___________________________________________ Zoran Vasiljevic, Vice President, CTO E-mail: mailto:zv...@ar... Web: http://www.archiware.com Phone: +49 89 319 084 98 Fax: +49 89 319 084 99 S-mail: ArchiWare(R) GmbH Gutenbergstr. 3 D-85716 Munich, Germany ___________________________________________ PresSTORE(R) - Backup Synchronize Archive |
|
From: Zoran V. <zv...@ar...> - 2005-02-12 16:17:20
|
On Saturday 12 February 2005 17:08, vl...@cr... wrote: mynsd > naviweb > nsdserver > nsweb > navicore > navisystem > > -------- Original Message -------- > To: nav...@li... > From: Zoran Vasiljevic <zv...@ar...> > Subject: [naviserver-devel] name ideas > > > Personally, I have no problem with naviserver but > just in case we'd need to change it, what about: > > naviengine > navihttpd > neohttpd > > (to be continued...) > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > > > > -- With kind regards, Mit besten Gruessen, Meilleures Salutations, ___________________________________________ Zoran Vasiljevic, Vice President, CTO E-mail: mailto:zv...@ar... Web: http://www.archiware.com Phone: +49 89 319 084 98 Fax: +49 89 319 084 99 S-mail: ArchiWare(R) GmbH Gutenbergstr. 3 D-85716 Munich, Germany ___________________________________________ PresSTORE(R) - Backup Synchronize Archive |
|
From: <vl...@cr...> - 2005-02-12 16:10:29
|
naviweb nsdserver nsweb navicore navisystem -------- Original Message -------- To: nav...@li... From: Zoran Vasiljevic <zv...@ar...> Subject: [naviserver-devel] name ideas Personally, I have no problem with naviserver but just in case we'd need to change it, what about: naviengine navihttpd neohttpd (to be continued...) ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ naviserver-devel mailing list nav...@li... https://lists.sourceforge.net/lists/listinfo/naviserver-devel |
|
From: <vl...@cr...> - 2005-02-12 15:59:24
|
Fine with me -------- Original Message -------- To: nav...@li... From: Zoran Vasiljevic <zv...@ar...> Subject: Re: [naviserver-devel] Wich source to start from, 4.0 or 4.1? On Friday 11 February 2005 07:01, Stephen Deasey wrote: > Hmm, I don't know that it would be the best idea to start with what I > (or Vlad) has. My repo is aolserver-HEAD as of a few months ago, > before the last set of major changes. > > I'd rather split my stuff up and submit it separately, have you guys > look it over before I apply it. I'm sure there are errors you will > spot and improvements you will suggest. And I don't think it will be > too hard to do. > > Also, I might re-evaluate some of my decisions. Obviously, when it's > just for yourself you can be a little looser in how you do certain > things, change APIs etc., because you know all the callers of the code > or can decide that you're happy with the disruption it might cause. I > haven't done anything drastic! But still, I'd want to be a little > more careful and, the tracker provides a nice paper trail. Good. So we could start with what is in the cvs for 4.0 now. I've checked out the 40_r10 out of CVS. I can import this clean, rewind the ChangeLog and start from there. Here some rought guidelines we should follow (feel free to change and/or add your own) Any functional-level changes should be posted as RFE's and we should all agree on them before we apply them to the codebase. Bugs we discover should be tracked in our bugbase and fixed accordingly. It would be nice if we can post a bug-report to AS project as well. Functional chages applied to the aolserver pendant project are to be discussed between us shortly and then we can decide if this is something we might need to have or not. Bugfixes applied to the aolserver pendant project could/should be also fixed here. I think we all can share this work on as-can basis. This is fair for the begining, I suppose. Later on, if we get more people on the wagon, we can always work-out some other procedure. Regarding CVS import: should I import the 4.0.10 state? Cheers, Zoran ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ naviserver-devel mailing list nav...@li... https://lists.sourceforge.net/lists/listinfo/naviserver-devel |
|
From: Zoran V. <zv...@ar...> - 2005-02-12 13:59:57
|
On Friday 11 February 2005 07:01, Stephen Deasey wrote: > Hmm, I don't know that it would be the best idea to start with what I > (or Vlad) has. My repo is aolserver-HEAD as of a few months ago, > before the last set of major changes. > > I'd rather split my stuff up and submit it separately, have you guys > look it over before I apply it. I'm sure there are errors you will > spot and improvements you will suggest. And I don't think it will be > too hard to do. > > Also, I might re-evaluate some of my decisions. Obviously, when it's > just for yourself you can be a little looser in how you do certain > things, change APIs etc., because you know all the callers of the code > or can decide that you're happy with the disruption it might cause. I > haven't done anything drastic! But still, I'd want to be a little > more careful and, the tracker provides a nice paper trail. Good. So we could start with what is in the cvs for 4.0 now. I've checked out the 40_r10 out of CVS. I can import this clean, rewind the ChangeLog and start from there. Here some rought guidelines we should follow (feel free to change and/or add your own) Any functional-level changes should be posted as RFE's and we should all agree on them before we apply them to the codebase. Bugs we discover should be tracked in our bugbase and fixed accordingly. It would be nice if we can post a bug-report to AS project as well. Functional chages applied to the aolserver pendant project are to be discussed between us shortly and then we can decide if this is something we might need to have or not. Bugfixes applied to the aolserver pendant project could/should be also fixed here. I think we all can share this work on as-can basis. This is fair for the begining, I suppose. Later on, if we get more people on the wagon, we can always work-out some other procedure. Regarding CVS import: should I import the 4.0.10 state? Cheers, Zoran |
|
From: Zoran V. <zv...@ar...> - 2005-02-12 09:56:53
|
Personally, I have no problem with naviserver but just in case we'd need to change it, what about: naviengine navihttpd neohttpd (to be continued...) |
|
From: Vlad S. <vl...@cr...> - 2005-02-11 14:20:22
|
Here is the tarball with my changes, i also removed root restriction from nsmain. ftp://ftp.crystalballinc.com/pub/vlad/aolserver-4.0.10-vlad.tar.gz We can put aside multiprotocol issue for a while and do other improvements, so once Jim will come up with something or we will be ready to roll out our implementation we put it into main codebase. Anyway our both changes are more like hacks, at least mine is to keep main http stuff working, so i will need to re-evaluate how i want to have multiprotocol now. But having CVS up and running will give us something to work on Stephen Deasey wrote: > Hmm, I don't know that it would be the best idea to start with what I > (or Vlad) has. My repo is aolserver-HEAD as of a few months ago, > before the last set of major changes. > > I'd rather split my stuff up and submit it separately, have you guys > look it over before I apply it. I'm sure there are errors you will > spot and improvements you will suggest. And I don't think it will be > too hard to do. > > Also, I might re-evaluate some of my decisions. Obviously, when it's > just for yourself you can be a little looser in how you do certain > things, change APIs etc., because you know all the callers of the code > or can decide that you're happy with the disruption it might cause. I > haven't done anything drastic! But still, I'd want to be a little > more careful and, the tracker provides a nice paper trail. > > I really think we're sort of stuck for the moment re the protocols > stuff. I'm hoping that what ever Jim is doing will be public soon so > we can make some informed decisions. > > If you do desperately want a tarball or something, I guess I can send > that along. > > > > On Thu, 10 Feb 2005 10:10:58 +0100, Zoran Vasiljevic <zv...@ar...> wrote: > >>On Wednesday 09 February 2005 21:59, Stephen Deasey wrote: >> >>>The question was, do we start with 4.0 or 4.1? >>> >>>On reflection, I think 4.0 would be best. Multiprotocol support is up >>>in the air anyway until Jim makes a move, and 4.1 has bugs with adp >>>etc. 4.0 will give us a stable codebase to start making changes. >>> >>>Merging 4.1 later will be good practice... :-) >> >>OK. This is the statement. >> >>I think one idea would be to get one of yours versions in the >>CVS since you did change (I believe) much more in the code >>than I did. I can then apply, after getting some RFE's in >>(for the better tracking and cocumentation) and clearing it with >>you, some of the minor things I have sitting. >> >>Maybe it would be also goog for you and Vlad to exchange tarballs >>and look if there are any major collisions prior to commiting >>the CVS. >> >>Zoran >> > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |
|
From: Stephen D. <sd...@gm...> - 2005-02-11 06:01:40
|
Hmm, I don't know that it would be the best idea to start with what I (or Vlad) has. My repo is aolserver-HEAD as of a few months ago, before the last set of major changes. I'd rather split my stuff up and submit it separately, have you guys look it over before I apply it. I'm sure there are errors you will spot and improvements you will suggest. And I don't think it will be too hard to do. Also, I might re-evaluate some of my decisions. Obviously, when it's just for yourself you can be a little looser in how you do certain things, change APIs etc., because you know all the callers of the code or can decide that you're happy with the disruption it might cause. I haven't done anything drastic! But still, I'd want to be a little more careful and, the tracker provides a nice paper trail. I really think we're sort of stuck for the moment re the protocols stuff. I'm hoping that what ever Jim is doing will be public soon so we can make some informed decisions. If you do desperately want a tarball or something, I guess I can send that along. On Thu, 10 Feb 2005 10:10:58 +0100, Zoran Vasiljevic <zv...@ar...> wrote: > On Wednesday 09 February 2005 21:59, Stephen Deasey wrote: > > The question was, do we start with 4.0 or 4.1? > > > > On reflection, I think 4.0 would be best. Multiprotocol support is up > > in the air anyway until Jim makes a move, and 4.1 has bugs with adp > > etc. 4.0 will give us a stable codebase to start making changes. > > > > Merging 4.1 later will be good practice... :-) > > OK. This is the statement. > > I think one idea would be to get one of yours versions in the > CVS since you did change (I believe) much more in the code > than I did. I can then apply, after getting some RFE's in > (for the better tracking and cocumentation) and clearing it with > you, some of the minor things I have sitting. > > Maybe it would be also goog for you and Vlad to exchange tarballs > and look if there are any major collisions prior to commiting > the CVS. > > Zoran > |
|
From: Stephen D. <sd...@gm...> - 2005-02-11 05:50:50
|
On Wed, 9 Feb 2005 13:34:53 +0100, Zoran Vasiljevic <zv...@ar...> wrote: > So, we have first RFE: 1119257 > > Stephen, how far are you with the alternate > cache implementation (you mentioned this in > todo list already, IIRC)? Great, you picked an easy one to start with :-) Kinda sucks my first contribution will be some untested work in progress, but I'll attach what I have to that ticket and add a comentary soon. |
|
From: Stephen D. <sd...@gm...> - 2005-02-11 05:47:17
|
On Wed, 9 Feb 2005 12:33:07 +0100, Zoran Vasiljevic <zv...@ar...> wrote: > > To show that I'm really not scared about the unpleasant work > I will actually start on a completely different end: docs. > I hate the current status more than anything else. > I need html references and man pages as well. The only thing > which I see could simplify this, is either Perl POD or Tcl doctools. > I've tried the XML already and have abandoned it (too complex). > Of course, I'm inclinded to doctools since already used by myself > in the threading extension. > Do you guys have anything against I go and collect the Tcl-API > (ns_xxx) commands and give them doctools treatment? The C-API > can wait for the moment... > Or, do you have some other ideas/sugestions concerning the format? You're a brave man, Zoran :-) I have no experience with Tcl doctools, but as long as it's easy and there is some kind of framework where it's obvious what I have to do to add a couple of extra functions, that would be great. Rather you than me! |
|
From: Vlad S. <vl...@cr...> - 2005-02-10 16:08:45
|
My Cox cable died last night, so i have no acces to the Internet from home till Monday, i hope, could be longer. I have 4.0.10 version with new binder, modified ns_socklisten from 4.1 and hacked UDP support. All changes are transparent, webserver still works as usual, so we can start with it. Multiprotocol there is as small as possible, but i started separatting Conn and Sock handling already, being able to allocate Conn and submit data to it to be run by conn thread is my goal. In this case, all drivers can be developed easily without hacking the core, even from Tcp Callback you can submit your data to conn queue, just pass Driver which will handle the protocol. The issue how i can get the sources from my home, not sure i have event floppies, will have to use laptop as transfer media:-))) Zoran Vasiljevic wrote: > On Wednesday 09 February 2005 21:59, Stephen Deasey wrote: > >>The question was, do we start with 4.0 or 4.1? >> >>On reflection, I think 4.0 would be best. Multiprotocol support is up >>in the air anyway until Jim makes a move, and 4.1 has bugs with adp >>etc. 4.0 will give us a stable codebase to start making changes. >> >>Merging 4.1 later will be good practice... :-) > > > OK. This is the statement. > > I think one idea would be to get one of yours versions in the > CVS since you did change (I believe) much more in the code > than I did. I can then apply, after getting some RFE's in > (for the better tracking and cocumentation) and clearing it with > you, some of the minor things I have sitting. > > Maybe it would be also goog for you and Vlad to exchange tarballs > and look if there are any major collisions prior to commiting > the CVS. > > Zoran > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel -- Vlad Seryakov 571 262-8608 office vl...@cr... http://www.crystalballinc.com/vlad/ |
|
From: Zoran V. <zv...@ar...> - 2005-02-10 11:01:08
|
On Wednesday 09 February 2005 22:04, Stephen Deasey wrote: > Hmm, that didn't work . Mailman experts feel free to step right up... Well, it seems it did! Just posted a reply on one of the RFE's and got thru without extra approval email sent to me (yet). Zoran |
|
From: Zoran V. <zv...@ar...> - 2005-02-10 09:14:12
|
On Wednesday 09 February 2005 21:59, Stephen Deasey wrote: > The question was, do we start with 4.0 or 4.1? > > On reflection, I think 4.0 would be best. Multiprotocol support is up > in the air anyway until Jim makes a move, and 4.1 has bugs with adp > etc. 4.0 will give us a stable codebase to start making changes. > > Merging 4.1 later will be good practice... :-) OK. This is the statement. I think one idea would be to get one of yours versions in the CVS since you did change (I believe) much more in the code than I did. I can then apply, after getting some RFE's in (for the better tracking and cocumentation) and clearing it with you, some of the minor things I have sitting. Maybe it would be also goog for you and Vlad to exchange tarballs and look if there are any major collisions prior to commiting the CVS. Zoran |
14 messages has been excluded from this view by a project administrator.
