QUESTION: Serving a File instead of a JSON/XML response about go-restful HOT 4 CLOSED

OK I did it in this way and seems to be working:

func serveSequence(request *restful.Request, response *restful.Response) {
id := request.PathParameter("seat-id")

rootdir, _ := os.Getwd()
filename := strings.Join([]string{id, ".zip"}, "")
http.ServeFile(response.ResponseWriter, request.Request, path.Join(rootdir, filename))

}

But I will like to serve the file as a different flavor for the same resource.. just like the library do with JSON, XML. Maybe writing a special WriteX function on the response.go code.

What are your thoughts about this?

from go-restful.

Your solution is exactly what I had in mind.
What do you mean with a different flavor? Can you give an example of a resource? and a corresponding WriteX

from go-restful.

About different flavor I was thinking on something like:

Produces(restful.MIME_JSON, restful.MIME_XML, restful.MIME_ZIP)

and then somehow create a custom WriteZip function and plugin it to the web service so I'm able to map the same route to the 3 formats... (including the zip file). In my current code I just create another restful.WebService with a completely different path.

So instead of having:

/seats/seat-id and /sequences/seat-id (for the ZIP file)

I will like to have:

/seats/seat-id and respond with JSON or the ZIP file according to the given Accept header.

I don't know if that makes sense.. maybe a feature request for the future?

Anyway thanks for your answer at least I know that my current solution is the way to go at the moment. Thanks.

from go-restful.

Ok, I understand your need. Adding other MIME types and associate them to their functions is something I would like to add. In particular I need support for Google Protocol Buffers.

from go-restful.