Re: When and when not to override Resource.init

Thanks a lot Joe for this nice demonstration! I'm totally convinced. I think also the init method must be removed from the normal constructor. best regards, Thierry Boileau On 10/22/07, Joe Nellis [EMAIL PROTECTED] wrote: Ok, well I just want to make sure you know what I'm talking about. I

Re: New 1.0 snapshot available

Jerome Louvel contact at noelios.com writes: As we are getting close to releasing a 1.0.6 and have already fixed a couple of issues, I thought it would be useful to provide a testable snapshot: http://www.restlet.org/downloads/1.0/current.zip - ChallengeRequests with a null realm are

RE: New 1.0 snapshot available

Hi Sumit, Thanks for this snapshot of 1.0.6. I confirmed that the null realm bug has been fixed. Thanks. Cool. [...] I cannot call Component.stop() to stop the Clients and Servers because it wants to make sure that the Component is started before calling stop() on the

RE: When and when not to override Resource.init

Hi all, I agree with Joe's remark too. I have made the change locally to the Resource and Handler classes. I will check that in when I'm done with the Resource refactoring. We won't port that change back to 1.0 as it slightly modifies the API contract. Best regards, Jerome -Message