Is this is the correct REST approach?

[mazdotnet]

Hi guys,

I need some architecture design verification. We have a site on shared
hosting so I can not use ISAPI filters to do any URL redirecting..etc.
We need to allow our end users to access some data so they can display
it on their site. I've been reading a lot of REST which is really easy
to use. However, I have some questions,
1. All the example have a the URL as http://www.mysite.com/rest/people
to return a list of people. Can I have it as http://www.mysite.com/rest/people.aspx?
I can easy create folder 'people' and have the code in default.aspx
then they can access it by http://www.mysite.com/rest/people
2. Is it ok to make it so that our end users do a POST to that URL and
then return back XML
3. Do I still have to pass the USERNAME/PASSWORD in every call?

Am I on the right track here? Is this still considered a REST
Service?

Thank you and I really appreciate your feedback
Maz.

[Cor Ligthert[MVP]]

MazdoNet,

You cannot do anything with that page as it only is giving back a 404 error.

As you use ASPNet then you have only one time to log on as you can save
username and password in a session item.

Cor

"mazdotnet" <ma*******@gmail.comschreef in bericht
news:ba**********************************@s50g2000 hsb.googlegroups.com...

Hi guys,

I need some architecture design verification. We have a site on shared
hosting so I can not use ISAPI filters to do any URL redirecting..etc.
We need to allow our end users to access some data so they can display
it on their site. I've been reading a lot of REST which is really easy
to use. However, I have some questions,
1. All the example have a the URL as http://www.mysite.com/rest/people
to return a list of people. Can I have it as
http://www.mysite.com/rest/people.aspx?
I can easy create folder 'people' and have the code in default.aspx
then they can access it by http://www.mysite.com/rest/people
2. Is it ok to make it so that our end users do a POST to that URL and
then return back XML
3. Do I still have to pass the USERNAME/PASSWORD in every call?

Am I on the right track here? Is this still considered a REST
Service?

Thank you and I really appreciate your feedback
Maz.