From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
Error 404--Not Found
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
A handful of vendors and analysts has launched a group called the Service Creation Community with the intention of helping service providers roll out new services faster.
So far they have just sketched out what they plan to do:
= Design templates for delivering new services.
= Resolve interoperability issues among members' gear.
The Service Creation Community is demonstrating a video on demand service here at SuperComm that includes gear from 11 of the members and say they are discussing more during the show. They even have a Web site www.servicecreation.org that you can check out.
Historically, this type of consortium pops up from time to time and runs out of steam in a year or two, but the point man for the group, net.com's president and CEO Bert Whyte, says that won't be the case here. He urges people to keep them active. "Demand demonstrations. Ask 'What has the Service Creation Community done for me lately?" Whyte said.