Re: Porting dbXML to Avalon

2001-09-02 Thread Peter Donald
On Sun, 2 Sep 2001 06:19, Tom Bradford wrote: > The next version of dbXML (1.5) will be ported from the Juggernaut > server framework to Avalon. From a very high level, it looks like it > should be fairly easy, but I was wondering if anybody has run into any > gotchas porting between server framew

Re: Porting dbXML to Avalon

2001-09-02 Thread Peter Donald
On Sun, 2 Sep 2001 09:38, Paul Hammant wrote: > If you can mine this maillist you'll see Peter and Fede ++ discussing > things about six months ago. Configurable and Reconfigurable. Perhaps > you need a ConfigurationUpdate interface .. > > interface ConfigurationUpdater { > void setConfiguratio

Re: Porting dbXML to Avalon

2001-09-01 Thread Tom Bradford
Paul Hammant wrote: > You've beaten it already then I think. Start by having a look > HelloWorldServer or some of the others. Wehn starting new blocks, I > invariable clone one of these and make it what I want (iteratively). > > "top-level object graph" Not sure what you mean here. Just mean th

Re: Porting dbXML to Avalon

2001-09-01 Thread Paul Hammant
Static is the killer. I guess only beginners make that mistake. No singletons needed for Avalon/phoenix. Can you elaborate a little? In the Juggernaut framework (which I designed about 4-5 years ago) there is a single static instance of a kernel just by virtue of the VM only creating one in the

Re: Porting dbXML to Avalon

2001-09-01 Thread Tom Bradford
Paul Hammant wrote: > Static is the killer. I guess only beginners make that mistake. No > singletons needed for Avalon/phoenix. Can you elaborate a little? In the Juggernaut framework (which I designed about 4-5 years ago) there is a single static instance of a kernel just by virtue of the VM

Re: Porting dbXML to Avalon

2001-09-01 Thread Paul Hammant
The next version of dbXML (1.5) will be ported from the Juggernaut server framework to Avalon. From a very high level, it looks like it should be fairly easy, but I was wondering if anybody has run into any gotchas porting between server frameworks. I guess I am chief porter for the mo ;-) Sta

Re: Porting dbXML to Avalon

2001-09-01 Thread Peter Donald
On Sun, 2 Sep 2001 06:19, Tom Bradford wrote: > The next version of dbXML (1.5) will be ported from the Juggernaut > server framework to Avalon. From a very high level, it looks like it > should be fairly easy, but I was wondering if anybody has run into any > gotchas porting between server frame

Re: Porting dbXML to Avalon

2001-09-01 Thread Peter Donald
On Sun, 2 Sep 2001 09:38, Paul Hammant wrote: > If you can mine this maillist you'll see Peter and Fede ++ discussing > things about six months ago. Configurable and Reconfigurable. Perhaps > you need a ConfigurationUpdate interface .. > > interface ConfigurationUpdater { > void setConfigurati

Re: Porting dbXML to Avalon

2001-09-01 Thread Tom Bradford
Paul Hammant wrote: > You've beaten it already then I think. Start by having a look > HelloWorldServer or some of the others. Wehn starting new blocks, I > invariable clone one of these and make it what I want (iteratively). > > "top-level object graph" Not sure what you mean here. Just mean t

Re: Porting dbXML to Avalon

2001-09-01 Thread Paul Hammant
> > >>Static is the killer. I guess only beginners make that mistake. No >>singletons needed for Avalon/phoenix. >> > >Can you elaborate a little? In the Juggernaut framework (which I >designed about 4-5 years ago) there is a single static instance of a >kernel just by virtue of the VM only cre

Re: Porting dbXML to Avalon

2001-09-01 Thread Tom Bradford
Paul Hammant wrote: > Static is the killer. I guess only beginners make that mistake. No > singletons needed for Avalon/phoenix. Can you elaborate a little? In the Juggernaut framework (which I designed about 4-5 years ago) there is a single static instance of a kernel just by virtue of the VM

Re: Porting dbXML to Avalon

2001-09-01 Thread Paul Hammant
> > >The next version of dbXML (1.5) will be ported from the Juggernaut >server framework to Avalon. From a very high level, it looks like it >should be fairly easy, but I was wondering if anybody has run into any >gotchas porting between server frameworks. > I guess I am chief porter for the m