News for hackers. Stuff that matters.

A comment on We have broken HTTP. Parent comment

Re:We have broken HTTP by bjt on Sunday January 11, 2015 @05:05PM (#8871522)
Looks a lot like the resource names on AWS [1]

<!-- AWS Elastic Beanstalk application version --> arn:aws:elasticbeanstalk:us-east-1:123456789012:environment/My App/MyEnvironment

<!-- IAM user name --> arn:aws:iam::123456789012:user/David

<!-- Amazon RDS tag --> arn:aws:rds:eu-west-1:001234567890:db:mysql-db

<!-- Amazon S3 bucket (and all objects in it)--> arn:aws:s3:::my_corporate_bucket/*

http://docs.aws.amazon.com/general/latest/gr/aws-arns-and-na...

[ Parent | on HN ]
Re:We have broken HTTP by eropple on Sunday January 11, 2015 @05:48PM (#8871644)
It should. There's a reason for that. :)
[ Parent | on HN ]
Re:We have broken HTTP by danellis on Sunday January 11, 2015 @11:45PM (#8872547)
What's the reason, and why didn't they just use URNs?
[ Parent | on HN ]
Re:We have broken HTTP by eropple on Monday January 12, 2015 @02:49PM (#8875982)
The reason is because they're based off the same principle. "ARN" stands for "Amazon Resource Name".

I don't know why they didn't use URNs. Probably because nobody else does.

[ Parent | on HN ]
Re:We have broken HTTP by pluma on Monday January 12, 2015 @08:17AM (#8873705)
I think the implication is meant to be "they look like URNs because they are".
[ Parent | on HN ]
Re:We have broken HTTP by wtbob on Monday January 12, 2015 @09:31AM (#8874012)
Except that they're not; rather, they're ARNs. URNs must begun with 'urn:'. It doesn't make a lot of sense that they're not URNs, but…they're not.
[ Parent | on HN ]
Re:We have broken HTTP by eropple on Monday January 12, 2015 @02:50PM (#8875990)
My guess: "nobody uses URNs generally, so might as well save four bytes off every one?"
[ Parent | on HN ]