Dear Jeppe, Thanks! A quick test shows that
>curl -o test.txt http://localhost:8080/biosimilarity-services/grammar/banana-cream-pie?file=file:// <pathToFile> also results in test.txt containing banana-cream-pie. As for the latter comment, i'm writing an URL-passing protocol. That is, the service is being told the URL for a resource -- which it will use subsequently. That's still well within RESTful doctrine ;-). Best wishes, --greg On Mon, Feb 15, 2010 at 1:38 PM, Jeppe Nejsum Madsen <[email protected]>wrote: > On Mon, Feb 15, 2010 at 10:34 PM, Meredith Gregory > <[email protected]> wrote: > > Dear David, > > Thanks! > > So, what's the recommended way of building a headless RESTful webservice > > that takes parameters? > > You could use normal url parameters: > > biosimilarity-services/grammar/banana-cream-pie?file=xx&file2=yy&file3=zz > > But a more idiomatic way is probably to use the uri to represent the > resources. But whole Phd dissertations have been written about this > :-) > > /Jeppe > > -- > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<liftweb%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > > -- L.G. Meredith Managing Partner Biosimilarity LLC 1219 NW 83rd St Seattle, WA 98117 +1 206.650.3740 http://biosimilarity.blogspot.com -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
