is anyone using RSS/RDF/XML

[fusionx]

for trades/syndication, etc? I don't think I've ever seen it in the adult industry yet.

How about web services?

[fusionx]

actually, I have seen one - one I built to syndicate porn star reviews for a client..

[lEricPl]

I pull about 10 different mainstream RSS 2.0 feeds from different sites to build content on my mainstream site.

[lEricPl]

Web Services are much more powerful in other ways instead of just to distribute content.

If all you want to do is distribute content thats what xml/rss is for.

[lEricPl]

I have built some neat XML Web Services over the last year.

Remote POP3 Server Email Validation engine
LinkGrabbers
IP/Country identification engine

etc.

[fusionx]

that rocks ericp

I've seen people building screen scrapers, pulling in remote URLs and parsing the contents, etc... RSS is so much easier. Even WDDX would work in most cases. Just wrap a security scheme around it and let 'er rip.

[lEricPl]

Yeah...


Of course is you need to auth. pullers of your feed against a members database, an XML Web Service would be the way to go. Just call your auth. method from the called function either returning content or an error status...passing the username/password as parameters when you call the function. I never really had a need to do this as of yet...but it is not difficult to do.

I have been researching 'Indigo' from MS a lot.
Some very interesting things are due for release in 2005/2006.

[lEricPl]

What I love most about XML Web Services is being able to keep most of the logic/code on my server. Let's say I build a desktop app that I want to lease to a client of mine for $50.00 a month.

I can either use an XML Web Service to check his membership before he runs the application...make sure he's all paid up....or even better...keep all major application functions in the remote XML Web Service and with each call to the service make sure they are a real client. Using this method you can track/count each User/IP address that uses the service.

If they abuse the app...or it runs from too many IP addresses...simply deny access to the main functions.

Of course...you can use this same system in Web Applications too...

[notjoe]

Originally posted by lEricPl
What I love most about XML Web Services is being able to keep most of the logic/code on my server. Let's say I build a desktop app that I want to lease to a client of mine for $50.00 a month.

I can either use an XML Web Service to check his membership before he runs the application...make sure he's all paid up....or even better...keep all major application functions in the remote XML Web Service and with each call to the service make sure they are a real client. Using this method you can track/count each User/IP address that uses the service.

If they abuse the app...or it runs from too many IP addresses...simply deny access to the main functions.

Of course...you can use this same system in Web Applications too...

It's all great until they spoof your host and provide their own XML feed and do as they wish with your program, kind of like SendSafe

[lEricPl]

Not if the core functions are on my server

I would be able to track every single call to the core functions.

I would be able to ban any username/IP as I wish.

The program would be useless without the core functions.

[lEricPl]

It's simple man...

You give the end user a Thin Client...either an .exe or a .dll.

All core functions of the program would be on the remote server.

There would be no cracking it becuase you could track each and every call to the core fuctions.

[lEricPl]

Of course...this all depends on what the app does