Well, I guess generally the 202 is used more for PUT/POST/DELETE
operations. Basically, it is informing the client to close the
connection and not wait for a different response because doing so would
tie up the line. Included in the response should be some indication of
how long a client
My last message was stupid. Please ignore. :)
What I was _trying_ to get at was this:
There Exists a Function which Relates en = de.
Ie. When you write down /en/de/ you are suggesting that in order to go
to de, you have to go through en. That is, you start at 'en' (the
original document)
At Thu, 19 Jul 2007 08:58:41 -0600,
Adam Taft [EMAIL PROTECTED] wrote:
My last message was stupid. Please ignore. :)
What I was _trying_ to get at was this:
There Exists a Function which Relates en = de.
[…]
From http://www.ietf.org/rfc/rfc3986.txt (URI generic syntax) sec.
1.2.3.
|
Erik Hetzner wrote:
Which is of greater significance: the language translated from or
language translated to? If you can’t answer that question, and I don’t
think that you can, then you don’t have a hierarchy.
Which is greater significance: manufacturer, model year, model class,
model type?
At Thu, 19 Jul 2007 13:48:35 -0600,
Adam Taft [EMAIL PROTECTED] wrote:
Which is greater significance: manufacturer, model year, model class,
model type? You said /cars/ford/2007/f-series/f-150/ was acceptable.
But, you can't answer which is more significant either. They are all
required to
I've designing my first restlet, and have all the basic
functionality in place. Previuosly, I had been looking
for a translation service, and google's is decent, but it
doesn't have a RESTful interface. So I wrote a little
scraper library and have built an asynchronous REST interface
on top
the number of
requests per IP during a given time period.
Best regards,
Jerome
-Message d'origine-
De : news [mailto:[EMAIL PROTECTED] De la part de Jason Hudgins
Envoyé : mercredi 18 juillet 2007 16:29
À : discuss@restlet.tigris.org
Objet : comments/feedback requested
I've designing my
[I must be getting old... you beat me to the punch! :-)]
FWIW, I totally concur with Adam on all counts.
Rock on,
John
On 7/18/07, Adam Taft [EMAIL PROTECTED] wrote:
[...]
Jason Hudgins wrote:
Glad you like the design. I originally had the language pairs as
query parameters like
At Wed, 18 Jul 2007 18:16:43 -0700,
John D. Mitchell [EMAIL PROTECTED] wrote:
FWIW to the intuition, rather than thinking whether or not it's
hierarchical it might be worth thinking of it in terms of being
ordered (as in order specific). In that case, the ordering of the
pair is critical.
Erik Hetzner wrote:
You beat me to it! Just to add, the RWS book suggests using commas for
ordered pairs in the URI design section, which makes sense to me.
Really?? That's weird. Wrong even?
I mean, if you can (or should) use commas, we'd have urls like this:
Jason Hudgins wrote:
I've had a few conversations where someone has expressed it
as a hierarchy. My intuition must work differently, I think of the
from and to as a pair where neither entity is the parent.
Very similar to the latitude and longitude examples for the geo
service in RWS.
Adam Taft wrote:
Erik Hetzner wrote:
You beat me to it! Just to add, the RWS book suggests using commas for
ordered pairs in the URI design section, which makes sense to me.
Really?? That's weird. Wrong even?
Not entirely - RWS only suggests it for pairing elements at the same
level of
Michael Terrington wrote:
Ordered does not necessarily mean hierarchical.
Hierarchy == Ordered, in my mind (particularly as it involves REST).
I mean, if we're talking about Hierarchy in the object oriented frame of
mind (ie. IS A type hierarchy), then maybe you have something. But,
we're
Adam Taft wrote:
Michael Terrington wrote:
Ordered does not necessarily mean hierarchical.
Hierarchy == Ordered, in my mind (particularly as it involves REST).
Agree, hierarchies are by their nature ordered.
I mean, if we're talking about Hierarchy in the object oriented frame of
mind
Michael Terrington michael at terrington.id.au writes:
That's ok, but it could be better. It would be better by including the
unique key in the original POSTed hierarchy. Ie.
../jobs/en/de/8fc66aca2ae1aa792ea35b8012acb6
(assuming that the original POST was to ../jobs/en/de/)
I
Michael Terrington wrote:
Absolutely, either is valid. I prefer to keep related things at the same level of hierarchy (i.e. the same folder).
Say there's thousands of these, would you still have them in one folder?
Hundreds of thousands? At which point do you change your thinking?
Actually, I do see one way I could leverage that. There is an additional
resource currently exposed that isn't in the docs. If you hit this URL :
http://www.incantations.net:8080/translate/jobs/ it will give you an ATOM 1.0
Correction, this is the URL to the ATOM feed :
Jason Hudgins wrote:
This begs the question though, are these list resources really all that useful?
Well, I think even though you haven't found a usefulness for those URLs
yet, doesn't mean that they may not be useful in the future.
Using a more natural organization for your data will
At Wed, 18 Jul 2007 19:41:09 -0600,
Adam Taft [EMAIL PROTECTED] wrote:
Really?? That's weird. Wrong even?
I mean, if you can (or should) use commas, we'd have urls like this:
/cars,ford,truck,f-series,f150,2007
instead of
/cars/ford/truck/f-series/f150/2007
That is a hierarchy, so it
Erik Hetzner wrote:
That is a hierarchy, so it should use slashes. Longitude,latitude is
not a hierarchy but a tuple, and they suggest for this commas.
So:
Longitude,Latitude == Latitude,Longitude ??
I'm legitimately asking. It does in real life, right? Same with things
like x,y
20 matches
Mail list logo
