@restlet.tigris.org
*Objet :* Re: Restlet 1.2 M2 released [throw previous email away]
I like the idea of having a default Extension for each MediaType, which
means that they are all mappable.
I understand the multiple uses of the word Extension, but my problem is the
multiple uses of Extension itself
Jerome,
I like the compactness of what you are proposing. My concern is orthogonal
to this, however, and I apologize if I'm making too much of a fuss over this
one point:
Relying exclusively on string values in annotations raises the possibility
of spelling errors that are not detected at
tant issue. I really hope other Restlet users will chime in
to express their opinion on this matter. Like Jerome, I'm very willing
to be convinced that my position creates more problems than it solves!
-Tal
Jerome Louvel wrote:
Tal,
Technologies ~ Co-founder ~ http://www.noelios.com/
http://www.noelios.com
_
De : Paul Austin [mailto:mail-li...@revolsys.com]
Envoyé : mardi 7 avril 2009 20:25
À : discuss@restlet.tigris.org
Objet : Re: Restlet 1.2 M2 released [throw previous email away]
Jerome,
I would be happy
Technologies ~ Co-founder ~ http://www.noelios.com/
http://www.noelios.com
_
De : Tal Liron [mailto:tal.li...@threecrickets.com]
Envoyé : mardi 7 avril 2009 20:35
À : discuss@restlet.tigris.org
Objet : Re: Restlet 1.2 M2 released [throw previous email away]
I like the idea
: Re: Restlet 1.2 M2 released [throw previous email away]
Hi Jerome-
I don't know, this whole extension thing sounds strange to me. Why replace
a well-defined, standardized namespace for media-types (e.g.
text/html etc) with a new, ad-hoc, non-standard namespace like this
extension stuff?
I
.org
Noelios Technologies ~ Co-founder~ http://www.noelios.com
De: Tal Liron
[mailto:tal.li...@threecrickets.com]
Envoy: mardi 7 avril 2009 20:35
: discuss@restlet.tigris.org
Objet: Re: Restlet 1.2 M2 released [throw previous email away]
I like the idea of havin
]
Envoyé : jeudi 2 avril 2009 19:16
À : discuss@restlet.tigris.org
Objet : Re: Restlet 1.2 M2 released
On Thu, Apr 2, 2009 at 12:13 PM, Rhett Sutphin rh...@detailedbalance.net
wrote:
On Apr 2, 2009, at 11:11 AM, Stephan Koops wrote:
Jonathan Hall schrieb:
Shame you can't have @Get
...@threecrickets.com]
Envoyé : vendredi 3 avril 2009 07:46
À : discuss@restlet.tigris.org
Objet : Re: Restlet 1.2 M2 released [throw previous email away]
Hi David,
I agree that filename extensions are not the best way to go here, but I see
nothing wrong with supporting them in addition to MIME types
loper ~ http://www.restlet.org
Noelios Technologies ~ Co-founder~ http://www.noelios.com
De: Tal Liron
[mailto:tal.li...@threecrickets.com]
Envoy: vendredi 3 avril 2009 07:46
: discuss@restlet.tigris.org
Objet: Re: Restlet 1.2 M2 released [throw previous email away]
Jerome,
I would be happy if users can choose to either use the extensions or the
mime-type where the extension is currently used. Consider a web service
which is designed to be used either from a web browser when the media=
parameter is used or from a Java client where the accept header can be
://www.noelios.com/
http://www.noelios.com
_
De : Tal Liron [mailto:tal.li...@threecrickets.com]
Envoyé : mardi 7 avril 2009 19:51
À : discuss@restlet.tigris.org
Objet : Re: Restlet 1.2 M2 released [throw previous email away]
Thanks for joining the discussion, Jerome, we were
ww.restlet.org
Noelios Technologies ~ Co-founder~ http://www.noelios.com
De: Tal
Liron [mailto:tal.li...@threecrickets.com]
Envoy: vendredi 3 avril 2009 07:46
: discuss@restlet.tigris.org
Objet: Re: Restlet 1.2 M2 released [throw previous email
Hi Jerome-
I don't know, this whole extension thing sounds strange to me. Why
replace a well-defined, standardized namespace for media-types (e.g.
text/html etc) with a new, ad-hoc, non-standard namespace like this
extension stuff?
I don't think that the goal of compactness is a good
: mercredi 1 avril 2009 18:08
À : discuss@restlet.tigris.org
Objet : Re: Restlet 1.2 M2 released
Excellent! I'm looking forward to seeing if the new Resource API simplifies
development.
Jerome Louvel wrote:
Hi all,
The second 1.2 milestone is out!
A complete coverage
Jonathan Hall schrieb:
Shame you can't have @Get(MediaType.TEXT_HTML). I don't know.
Would it work to change MediaType from class to an enum? That could
work, but I'm not sure
best regard
Stephan
--
Stephan Koops schrieb:
Jonathan Hall schrieb:
Shame you can't have @Get(MediaType.TEXT_HTML). I don't know.
Would it work to change MediaType from class to an enum? That could
work, but I'm not sure
While sending the email I remembered: You can't add new MediaTypes this
way, so
On Apr 2, 2009, at 11:11 AM, Stephan Koops wrote:
Jonathan Hall schrieb:
Shame you can't have @Get(MediaType.TEXT_HTML). I don't know.
Would it work to change MediaType from class to an enum? That could
work, but I'm not sure
This would sacrifice the ability to create new MediaTypes in
An alternative would be to have a MimeType class which had String constant
values for all the common MediaTypes, then you would only need to use
strings if you had a non common media type.
One other thing I've noticed that in some places the mime type is shortened
(e.g. xml instead of text/xml).
On Thu, Apr 2, 2009 at 12:13 PM, Rhett Sutphin rh...@detailedbalance.netwrote:
On Apr 2, 2009, at 11:11 AM, Stephan Koops wrote:
Jonathan Hall schrieb:
Shame you can't have @Get(MediaType.TEXT_HTML). I don't know.
Would it work to change MediaType from class to an enum? That could work,
The
MetadataService is what you're talking about. It translates between
strings and other useful dimensions (in this case, MediaType
instances). Right now, though, it only supports "extensions" as the
strings, which mean to be filename extensions. So that's why we have
"txt" as the shorthand
Stephan Koops wrote:
Stephan Koops schrieb:
Jonathan Hall schrieb:
Shame you can't have @Get(MediaType.TEXT_HTML). I don't know.
Would it work to change MediaType from class to an enum? That could
work, but I'm not sure
While sending the email I remembered: You can't add new
But it's not clear to me why this code should use the
MetadataService at all. The mapping of file extensions to
MediaTypes is one of the web's irritating but hard to avoid dirty
shameful secrets. The only time we should stoop so low as to base a
MediaType calculation on an extension name is if
Hi
David,
I
agree that filename extensions are not the best way to go here, but I
see nothing wrong with supporting them in addition to MIME types. As
for supporting MIME types, it seems we already have a facility in
Restlet via MediaType.valueOf():
Hi all,
The second 1.2 milestone is out!
A complete coverage is available in our blog:
http://blog.noelios.com/2009/04/01/restlet-12-m2-released/
http://blog.noelios.com/2009/01/23/restlet-12-m2-released/
Best regards,
Jérôme Louvel
--
Restlet ~ Founder and Lead developer ~
Excellent! I'm looking forward to seeing if the new Resource API
simplifies development.
Jerome Louvel wrote:
Hi all,
The second 1.2 milestone is out!
A complete coverage is available in our blog:
http://blog.noelios.com/2009/04/01/restlet-12-m2-released/
...@gmail.com]
Envoyé : mercredi 1 avril 2009 18:08
À : discuss@restlet.tigris.org
Objet : Re: Restlet 1.2 M2 released
Excellent! I'm looking forward to seeing if the new Resource API simplifies
development.
Jerome Louvel wrote:
Hi all,
The second 1.2 milestone is out!
A complete
27 matches
Mail list logo
