Hi Chris, This is a very interesting suggestion. Let me think more about it. For now, I agree that a filter could very well handle this job. http://restlet.tigris.org/issues/show_bug.cgi?id=151
Best regards, Jerome > -----Message d'origine----- > De : Chris Winters [mailto:[EMAIL PROTECTED] > Envoyé : vendredi 11 août 2006 16:14 > À : [email protected] > Objet : best place for creating usable inbound Representation? > > I see in AbstractHttpServerCall that we assign the input > representation > (what the client gives us) as an InputStream or ReadableByteChannel, > depending on what's available. What would be great is if I > was able to > register some sort of object to recognize the input (ideally based on > Content-Type) and translate it into a higher-level object for the > following components to use. > > Or is this best done within my application as a filter where I can do > something like this? > > public class InboundDataConversionFilter > extends AbstractFilter > { > @Override > protected void beforeHandle( Call call ) > { > HighLevelRepresentation hlr = > translateFromInputStream( call.getInput().getStream() ); > call.setInput( hlr ); > } > } > > Chris > > -- > Chris Winters ([EMAIL PROTECTED]) > Lead Software Developer > Vocollect Healthcare Systems > > CONFIDENTIAL, PRIVILEGED COMMUNICATION: This e-mail is private and > intended for the addressee(s) only. It may contain privileged and/or > confidential information. If you have received it in error > you are not > authorized to disseminate it in any manner; please delete it and any > copies and reply to the sender that it was misdirected. > > >
