Isn't web 2.0 to do with the design/appearance of the site? If so, then PHP has nothing to do with it.
Yeah, you are right, it has to do with design (not graphical) and usability of site. I just want a kind of start-up tutorial, just to have an idea.
Originally posted by Markus
Haven't seen you around much, Hsriat. Where've you been?
I started my post graduation, so got busy in that. Whzz up with ur studies?.. I hope u doing good. And I see you are moderator now... good! Keep it up mate ;) cya around.
This is a message for all of you who are wondering why so many Job ads and interviews ask you if you know PHP and then ask you something related to Web 2.0.
Web 2.0 doesn't exist. There's only one web. It is just a buzz word. Yes it is controversial (and this is my opinion), never-the-less there isn't really a solid definition for web 2.0
Basically what web 2.0 are trying to say is designing applications for the 21st century instead of static HTML.
They want eye-grabbing, easy to use, readable and attractive sites. (Usually everything is shiny and has reflections), but that's not all of it. They also mention AJAX and call non-alert-box type pop ups so that the website actually looks like an application. You can drag and drop things, etc.
To me it's just how technology progressed and what people like as the times go on (i.e. Windows 95 ---> Windows Vista) it has nothing to do with the web being changed. The internet is the same old internet, PHP is just PHP, HTML is still HTML and most importantly, JavaScript is still JavaScript.
Actually, Web 2.0 is a programming design philosophy that is designed to promote User contribution and sharing.
Web 2.0 sites make more use of comment blocks, networking, User ratings and reviews, that sort of thing, with the goal being that Users contribute a significant amount of the content on a site or application.
Web 2.0 is not incompatible with "Web 1.0". In fact, you generally need SOME kind of company-provided content to attract Users in the first place.
"Web 1.0":
- Posting articles.
- Tagging content.
- Put products online for sale.
Web 2.0:
- Allow Users to post comments and rate articles.
- Allow Users to tag the content themselves and create a tag cloud to let Users know which tags are more popular.
- Allow Users to post reviews and submit additional photos/videos of them using your company's products.
Thank you all for providing those details.
So I think may be I was using a vague term. By Web 2.0, I mean to say something similar to Facebook, in which third party developers can make their own application which will work on top of the framework of your application. That's the basic requirement in my case. So is that a part of so called "Web 2.0"?
Any idea where should I start for such stuff?
Originally posted by Markus
My studies? Unfortunately I have none. I left it too late to get into college and now I'm stuck with awful prospects. Get a job in tesco, they say.
:(
Ok don't worry, Tesco is good. I worked in Sainsbury for a couple of days :D
SOAP is generally the technology of choice for building web services, though if your application framework isn't particularly complicated, you could just use REST (Ajax-style HTTP requests).
So far, all of you are wrong in your description of "Web2.0". It has nothing to do with graphics or buttons or programming, etc. There is a perfectly logical definition of it and I'll find it for you later.
Web 2.0 is the business revolution in the computer industry caused by the move to the internet as platform, and an attempt to understand the rules for success on that new platform. Chief among those rules is this: Build applications that harness network effects to get better the more people use them. (This is what I've elsewhere called "harnessing collective intelligence.")
The original definition from Tim O'Reilly who coined the term.
Since so many had trouble figuring out the original idea above, here is his compact defintion:
Thanks for the actual definition. Much appreciated. :)
Originally posted by pbmods
Look at creating web services in PHP (http://www.google.com/search?q=php+we b+service).
SOAP is generally the technology of choice for building web services, though if your application framework isn't particularly complicated, you could just use REST (Ajax-style HTTP requests).
Thank you. I think I should head towards SOAP now.
Comment