Thanks Xavier, I’ve added those references to the specs page and classified the existing ones as well.
http://wiki.restlet.org/developers/172-restlet/g1/391-restlet.html Best regards, Jerome -- <http://www.restlet.org/> http://www.restlet.org http://twitter.com/#!/jlouvel De : Xavier Mehaut [mailto:[email protected]] Envoyé : mercredi 14 septembre 2011 12:29 À : Jerome Louvel Cc : discuss Objet : Re: Porting restlets in Go language bjr jerome some links of rest implementation in go : http://code.google.com/p/gorest/ https://github.com/Kissaki/rest.go#readme https://github.com/nathankerr/rest.go the first one is a nice implementation using go capabilities regards Envoyé de mon iPhone Le 14 sept. 2011 à 12:02, "Jerome Louvel" <[email protected]> a écrit : Hi Xavier, Thanks for the suggestion. Looking at the recent support for Go in Google App Engine, I think we should consider such a port in the middle term. Our priority right now is a JavaScript port, but next we could look into C-based languages like C#, Go and C++. I’ve updated our specification page accordingly: http://wiki.restlet.org/developers/172-restlet/g1/391-restlet.html The goal is to automate the maximum number of artifacts based on the Java main trunk, using our code customization tools and enhancing them. It would also be useful to start from a minimal manual port to ensure we have a clear target for code convertion/generation. Best regards, Jerome -- <http://www.restlet.org/> http://www.restlet.org http://twitter.com/#!/jlouvel De : [email protected] [mailto:[email protected]] De la part de Xavier Méhaut Envoyé : lundi 30 août 2010 08:40 À : [email protected] Objet : Porting restlets in Go language Hello, I know it is a little bit out of scope, but I would like to know if porting Restlets in Go language would interest someone. I'm quite sure that Go will become an important language in a foreseeable future, and its characteristics would suit perfectly for restlets too, especially its efficiency, its portability, its already abundant libraries (especially for network communications), and the simplicity of the language. Of course it couldn't be a one to one porting but we could keep concepts, and maybe a lot of api... What do you think about this proposal? regards Xavier ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2838464
