Hi Justin and Rob,

1) I agree with the confusing getEntityAsObject() name. 

Also I don't intent to let the API ossified. I want to maintain upward API
compatibility between two *subsequent* versions (major or minor) only. For
example the migration between 1.0 and 1.1 should be direct, with some
deprecated methods (still working). In version 1.2, all the methods
deprecated in 1.1 from 1.0 would be first removed. The only issue is for
people migrating from 1.0 to 1.2 without first going through 1.1. IMO, there
are more advantages than inconvenient.

Here is what I propose: 
 - deprecate the "getEntityAsObject():Object" method in 1.1
 - add "getConvertedEntity():Object" in 1.1
 - remove the "getEntityAsObject():Object" method in 1.2
 - add a "getEntityAsObject():ObjectRepresentation" method in 1.2

I've added a RFE:
http://restlet.tigris.org/issues/show_bug.cgi?id=360

2) Thanks for your help proposing regarding the documentation. We will try
to launch a Developer Guide effort ASAP. I want to build it with DocBook,
one XML document per chapter, all versionned in SVN and automatically
published on the Restlet.org web site. That will allow contributions via SVN
patches and publication to various output formats.

Best regards,
Jerome  

> -----Message d'origine-----
> De : Stanczak Group [mailto:[EMAIL PROTECTED] 
> Envoyé : jeudi 23 août 2007 18:13
> À : [email protected]
> Objet : Re: getEntityAsObject()?
> 
> I would be happy to help as well.
> 
> Rob Heittman wrote:
> >
> > > It does seem there is a lack of documentation. Is there 
> more some where?
> > > I think I've read most everything.
> >
> > A major documentation initiative is on the roadmap for later this 
> > year.  I think there will be lots of volunteers to help.
> >
> 
> -- 
> Justin Stanczak
> Stanczak Group
> 812-735-3600
> 
> "All that is necessary for the triumph of evil is that good 
> men do nothing."
> Edmund Burke

Reply via email to