From: Jeff R. <dv...@di...> - 2007-08-09 21:04:41
|
Is there a simple, concise, and comprehensive[*] list of specific incompatibilities between the current versions of ns and aolserver? I'm considering moving my aolserver code to naviserver, I want to know what pitfalls I can expect. Thanks, -J [*] - irony intentional :) |
From: Zoran V. <zv...@ar...> - 2007-08-10 09:03:14
|
Am 09.08.2007 um 23:04 schrieb Jeff Rogers: > Is there a simple, concise, and comprehensive[*] list of specific > incompatibilities between the current versions of ns and aolserver? > I'm considering moving my aolserver code to naviserver, I want to know > what pitfalls I can expect. There is no simple, concise and comprehensive list of specific incompatibilities unfortunately. The best thing is to fetch the cvs head, compile and give it a try. We wanted to tag the current cvs with 5.0 release but we are still lagging behind (my fault mostly). Command-wise (ns_*) it should be backwards compatible to 4.0 although we ported much of the interesting things from 4.5. We also improved quite a few of server internals but from the Tcl-API you should be more/less OK. C-API is in some places considerably changed but for most of the things we left older compatibility wrappers. Yet, so far I do not know anybody who tried to replace the AS with our code. Whatever, we would help you get it up and running if you like. Perhaps this is a good chance to start something like a compatibility-list. Cheers Zoran |
From: Gustaf N. <ne...@wu...> - 2007-08-10 09:42:20
|
Zoran Vasiljevic schrieb: > Yet, so far I do not know anybody who tried to replace > the AS with our code. Whatever, we would help you get > it up and running if you like. Perhaps this is a good chance > to start something like a compatibility-list. > For naviserver 4.99.1, the following changes were needed to run openacs on top of it. http://openacs.org/forums/message-view?message_id=1148743 maybe a first start for the list... -gustaf |
From: Stephen D. <sd...@gm...> - 2007-08-10 10:10:41
|
On 8/10/07, Gustaf Neumann <ne...@wu...> wrote: > Zoran Vasiljevic schrieb: > > Yet, so far I do not know anybody who tried to replace > > the AS with our code. Whatever, we would help you get > > it up and running if you like. Perhaps this is a good chance > > to start something like a compatibility-list. > > > For naviserver 4.99.1, the following changes were needed to run openacs > on top of it. > > http://openacs.org/forums/message-view?message_id=1148743 > > maybe a first start for the list... Do you have details? Most of these sound more like bugs or accidental changes. Don't work around bugs... :-) |
From: Gustaf N. <ne...@wu...> - 2007-08-10 10:30:45
|
Stephen Deasey schrieb: >> . >> >> Do you have details? Most of these sound more like bugs or accidental >> changes. Don't work around bugs... :-) >> from my referenced posting: > The argument passing for filters is different in naviserver, in addition, the useless conn arguments are removed. The details for the filters are in the diff. one example for the removed dummy connection argument is ns_headers. Grep for connid in aolserver nsd/tclresp. most are optional, but the question is, how serious one is about compatibility. are you saying, that ns_cache is now fully compatible in naviserver with the version in aolserver 4.5? -gustaf |
From: Stephen D. <sd...@gm...> - 2007-08-10 10:08:11
|
On 8/9/07, Jeff Rogers <dv...@di...> wrote: > Is there a simple, concise, and comprehensive[*] list of specific > incompatibilities between the current versions of ns and aolserver? > I'm considering moving my aolserver code to naviserver, I want to know > what pitfalls I can expect. > > Thanks, > -J > > [*] - irony intentional :) There shouldn't be anything huge. I don't recall us taking any genuinely useful or not-a-bug feature and deliberately breaking it. But there's been some changes... You will of course have to recompile any C modules you're using. We have ns_cache_* commands. But there's nothing stopping you from also loading the old ns_cache module. Vald imported a version of that into our CVS -- shout out if it doesn't work. We dropped the optional connid argument from many of the Tcl commands such as ns_register_proc and ns_return*, but this has been optional and deprecated in AOLserver since the last century so consider this an opportunity to update your old code :-) Mainly, the thing you're going to notice is that quite a lot has moved around in the config file. There's a sample-config.tcl but it could be better. One new feature we have here is logging of config values as they're accessed. Turn on dev level debugging and you can see exactly what the code is expecting to find as the server starts up. |