Hi Lars, You bring up a valid point. I had a similar concern initially, but creating another property seems overkill to me. Why not specify that this "attributes" property defines space shared between the framework and the user application?
Now comes the potential problem of conflict between attribute names, especially if we have to add new Restlet attributes in the future. Maybe we should specify that all names starting with "org.restlet" are reserved by the framework. Then I should rename "requestHeaders" to "org.restlet.requestHeaders" or maybe just "restlet.requestHeaders". Of course, this should be properly documented in the Javadocs. Would that address your concern? Best regards, Jerome > -----Message d'origine----- > De : Lars Heuer [mailto:[EMAIL PROTECTED] > Envoyé : mercredi 20 septembre 2006 13:35 > À : Jerome Louvel > Objet : Re: b19 - Call converters > > Hi Jerome, > > Sorry for my late reply. :) > > > I think you will be happy to know that I've found a simpler > solution. Now, > > the HTTP server|client connectors systematically pass the list of > > request|response headers as an attribute in the call's > attributes map. > > Looks promising. The only thing I like to bring to your attention: I > thought that the "attributes" property of the Call is an > user-controlled Map. The user can do whatever she wants to do > with it. > Now Restlet invades this user space. Since I am not using the > "attributes" property yet, it's no problem for me. But the users > should be aware of this Restlet behaviour. I'm not sure if this > intrusion legitimates another Call attribute that is controlled by > Restlet. > > Thanks for your work. :) > > Best regards, > Lars > -- > http://www.semagia.com > >
