Here's my take
Dave Winer: an essay to kick off the new year
Dave and I see some of the same data, but we interpret it differently. Here's my take.
Where interfaces are of the simple client/server kind, and where all the state is on the server, the trend I see for the future is that new interfaces will increasingly be defined as a simple HTTP GET.
When there is a wide range of clients implementations, some developers may choose to transcribe this document into machine readable forms, like XML schema and/or RELAX NG so that both static and dynamic bindings can be automatically generated for a wide range of programming environments. When there is a wide range of server implementations, others may write validators using tools as simple as XML parsers and regular expressions to ensure that the there is consistency, conformance to the specifications and that best practices are encouraged.
When there is anticipation of a wide range of clients or servers, then the protocol will be defined to be extensible so that it can be adapted to a wide range of purposes.
RSD is an example of such an interface that has started out along these lines. RSS 2.0 is an example of such an interface that has recently converged onto a similar path.
When the interfaces are simple client/server, but where most or all of the state is on the client, the trend I see for the future is that new interfaces will increasingly be defined as a simple HTTP POST. Human readable docs, and optional machine readable docs, validators, and extensibility characters will also be factors, for much of the same reason.
The TrackBack Specification and RSS validator SOAP interface are both examples of this.
The most important of the non-simple client/server interactions is one of alerts or notification. All sorts of DigID information will need to be added to the data in order to traverse the gauntlet of gateways required.
Once again, the data will be well formed XML, with docs of both human and machine readable forms, and with validators and extensibility provisions.
Once this is in place, polling mechanisms for things like RSS will be replaced with something a bit more bandwidth friendly.
After that, there are still more interesting usage scenarios to consider.
Just out of curiosity what are the security implications of using GET requests? When data is sent via POST the body of the message can be encrypted using SSL, but can the same be said for GET requests? Is the query of a GET request encrypted in the same fashion when the protocol is https? What about the fact the potentially protected information can make its way into the logfiles of servers (most log the request URL but do not log POSTed data). Thoughts?
Posted by Anthony Eden at
Anthony, when you're in HTTPS, the entire HTTP request is encrypted. You can still see that 2 entities are talking (traffic analysis could be a concern in some situations), but it's difficult to see what they're saying to each other. As far as the logfiles, I think you might have a valid concern there. One point that the REST people would bring up is that requesters shouldn't be held responsible for any side effects of a GET, so the request itself should be safe, though you might not want outsiders looking at the response data. I'd say that you have to couple channel encryption (SSL) with authentication, so that even if an outsider got ahold of a URL, they still couldn't complete a request without another piece of information. I think that you'd also need to make sure the GET request data itself isn't sensitive.
Posted by Gordon Weakliem at
Security is like performance, where the only valid answer is "it depends".
There may be cases where knowledge that there was a phone call from the whitehouse to the kremlin - independent of the content - would be sensitive.
Within the REST camp, there are degrees of acceptance as to whether the URL can encode client state or should be totally opaque. My leanings are towards being opaque to programs (but readible by humans). This leads towards the recommendation to use POST for requests that involve the transmittal of state information from the client to the server.
Posted by Sam Ruby at
Sam, all the stuff I talked about is working. Why should we break it and put it back together? It'll never happen. The next thing to do is to teach the world how to use this stuff to make money, improve education, get health information into the hands of people who need it, and overall improve the quality of human existence on this planet. Whether it's HTTP GET or something else makes absolutely no difference.
Posted by Dave Winer at
Dave, what is working today is too brittle.
Within two years, somebody, perhaps Userland perhaps somebody else, will invent a meta-meta weblog API, and the cycle will start over again.
Just look at the differences between what it has taken to evangelize 0.9x (where x>1) versions of RSS vs specific RSS 2.0 namespaces. Much better, eh?
The alternative I'm advocating is to define a simple XML formats, like RSD. Tell people how they can add whatever they need. From the documents you receive, take what you need and ignore the rest.
You've seen me operate for over a year now. I don't recommend breaking anything. But when things do break, I suggest that their replacements be less brittle than their predecessors.
Posted by Sam Ruby at
No Sam, I don't agree with your analysis. What's there works fine. Let's have a look in a while. I agree you don't recommend breaking things and for that I am thankful.
Posted by Dave Winer at
Don't we have this already?
Jeremy Allaire is points to an RFC to extend the MetaWeblog API to handle binary media. I thought the RFC that he highlights is generally misguided and reinvents the wheel. Hear me out. UPDATE: Sam Ruby makes some likeminded comments and issues a challenge to the MetaWeblog and Blogger API advocates.... [more]Trackback from tima thinking outloud. at
Here’s my take
More details at [link]
Earn Money on Internet have been divided into :
1) Earn Money with your Blog or Website (Recommended)
2) Earn Money through Affiliate Programs (Recommended)
3) Get Paid to take Online Surveys
4) Read Mails or Surf the Web
Earn Money Without Spend Money
Easy ways to earn money with Blog or Website !!!
follow step by step :
1. Create a blog with blogger.com
2. link exchange example : linkalizer , linkexchanged , gothimatch , religiousmall , linkadministrator , linkmachine and others
3. Join advertisement program, earn money with advertisement. example : adsense Google , revenuepilot , adbrite , bidvertiser , Text Link Ads and others
4. Join Affiliate program, earn money with affiliate program. example : SFI , clickbank , roiroket , LinkShare Affiliate! , CJ
5. Join Forums. Example : preCharge Community Forums , Free Advertising Blog
6. Join Articles. Example : article marketer ,
7. Join Press Releases : PRWeb.com , Pressbox.co.uk
8. Join Hit Exchanges. Example : trafficswarm , 123click , Hit Pulse
9. Join Building Network. Example : Your Luck List , 241Lead , Viral traffic list , List Dot Com
1) Earn Money with your Blog or Website
bidvertiser Place the BidVertiser text ads on your website and make money online by getting paid for every click.
adbrite Earn money by selling ads on your website
revenuepilot You receive 60% of what advertisers pay RevenuePilot per click. A variety of linking methods is available, including text links, banners, search boxes, javascript feed, dynamic banners, etc.
Text Link Ads You will get paid the first of every month and have the option of receiving a check or being paid via Paypal. We feature a 60 day cookie on all referrals.
Google Adsense Earn money while displaying advertisements on your Website. When visitors click on these ads, Google pays you. Along with targeted advertising for your content pages, you can add a Google search box to your site and show targeted ads on search results pages.
2) Earn Money through Affiliate Programs
CJ Over 1000 advertisement programs to choose from. Real-time tracking, reporting and analysis of impressions, get paid monthly by check, etc.
clickbank Promote Products & Earn Commission Today! Setup is free, fast and you’ll have instant access to over 10,000 products with commissions as high as 75%. You’ll appreciate our fast & accurate tracking system and dependable payment services. We’ve never missed a scheduled payment!
SFI You can make money every time someone makes a purchase at the stores you refer to NOC...for LIFE!
roiroket Targeted campaigns specific to YOUR Marketing needs , High Payouts on Performance Based Ad Campaigns ,Competitive, timely Payouts, Exclusive Destination Specific Offers Tailored to Your Audience , Highly Responsive Full Service Account Management Team
LinkShare Affiliate! you will earn revenue for driving sales, leads and traffic to partner sites. Find hundreds of affiliate programs from Fortune 500 and other leading businesses in the LinkShare Network
We will explain more details in the future as following :
1) What is a blog ?
2) How to create a blog ?
Example :
3) What we can take advantage from blog ?
4) Why ping a blog ?
5) How to ping a blog ?
6) How some people can make money & earn money over USD $ 20,000/month on the internet ?
USD $ 20,000.00 . Is it easy ??? . They just join advertisement and affiliate program (all is free).
7) How to submit your blog or website to search engine ?
BuildTraffic.net
8) How to promote blog or website on the internet ?
9) Advertisement on internet can be divided into 4 categories as below :
i) What is PPC advertisement ?
You get paid for every visitor that clicks on an ad. You to make as much as possible from your advertising space, by letting advertisers bid on your ad space.
ii) What is Pay Per Impression advertisement ?
Example : Paypopup , Adversal and Others
iii) What is Pay Per Lead advertisement ?
Example : Icoocash , clickcash and Others.
vi) What is Pay Per Install ?
Example : Teddycash , Matcash , yoursitebar, and Others.
10) What is Advertiser ?
Posted by lim kock chuan at
s/HTTP PUT/HTTP POST/ (at least to bring the text in alignment with your examples)
Posted by jim winstead at