Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Professional design advice needed

0 views
Skip to first unread message

mazdotnet

unread,
Apr 30, 2008, 4:49:45 PM4/30/08
to
Hi guys,

We have an events page in our company that's database driven and we
need to shared it with our partners. They need to pull information
from our site. They can be running asp, php, .jsp..etc. I was thinking
of using a web services and returning datatable (maybe to XML). Is
that the best approach? Or should I just take it as a Url parameter
and return an XML file? Any suggestions here would really help me.

I really appreciate your input on this.

Thanks
Maz

Mark Rae [MVP]

unread,
Apr 30, 2008, 4:58:06 PM4/30/08
to
"mazdotnet" <mafl...@gmail.com> wrote in message
news:6dda7d00-6ae0-42c6...@56g2000hsm.googlegroups.com...

> We have an events page in our company that's database driven and we
> need to shared it with our partners. They need to pull information
> from our site. They can be running asp, php, .jsp..etc. I was thinking
> of using a web services and returning datatable (maybe to XML). Is
> that the best approach? Or should I just take it as a Url parameter
> and return an XML file? Any suggestions here would really help me.

Definitely a web service, IMO.


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

bruce barker

unread,
May 1, 2008, 12:19:01 PM5/1/08
to
To allow the broadest coverage I'd use the REST interface (Web 2.0). Its
getting much more popular then web services (for open interfaces), as they
are easier to consume. Its basically a url/xml pattern (your first choice).

the url mapping module in the .net extensions (still beta) is designed to
support REST. also the new SQL Server Data Services (cloud) is REST based.


-- bruce (sqlwork.com)

Fernando Rodriguez

unread,
May 1, 2008, 8:58:03 PM5/1/08
to
I would go with the webservice, but instead of returning a dataset I would
return an array of structures (just create a class with a Title,
Description, and whatever other public properties needed and decorate it
with a [Serializable] attribute, and return an array of it).

That way it's easier to consume on other platforms other than NET.


"mazdotnet" <mafl...@gmail.com> wrote in message
news:6dda7d00-6ae0-42c6...@56g2000hsm.googlegroups.com...

0 new messages