GraphicRiver?
http://graphicriver.net
GraphicRiver is an Envato Marketplace. At GraphicRiver you can buy and sell royalty free layered Adobe Photoshop Files, Vector Graphics, Icon Sets and Add-ons for Adobe Photoshop and Illustrator. It's like having an entire graphics department at your fingertips!

Files are priced from just one dollar, based on the complexity, quality and use of the file. Anyone is free to sign up for an account and begin trading or purchasing files.

Other Envato Marketplaces include FlashDen, ThemeForest, VideoHive and AudioJungle.
The Team Our core staff are:

* Vahid - Chief
* Cyan - Marketplace Manager
* Jun - Money Man
* John - Lead Programming & Vocals
* Clinton - Bass Programming & Backup Vocals
* Erin - Keyboards & Backup Vocals
* James - Drum Programming
* Stuart - Band Stylist
* Collis - Mr Pixel
* Rodney - Radial Gradient Correspondent
* scottwills - AudioJungle Site Manager
* LanceSnider - FlashDen Site Manager
* AmandaLinder - GraphicRiver Site Manager
* JeffreyWay - ThemeForest Site Manager
* MarkBrodhuber - VideoHive Site Manager

Additionally we have some great members who review and feature items as well as provide support for files, monitor the forums and are generally awesome, they are:

* Aaron_Osteraas
* ADG3studios
* adrianpelletier
* AmandaLinder
* ArikB
* baf2681
* bgm
* envato
* flashjunkie
* JeffreyWay
* JimmyP
* joelfalconer
* kailoon
* LanceSnider
* loziosecchi
* MarkBrodhuber
* RimV
* SaafiDesign
* scottwills
* Slats
* Solidbeats
* xmdsys

Contact & Business Details

FlashDen Pty Ltd trading as Envato
ABN 11 119 159 741
PO Box 21177, Little Lonsdale Street, VIC 8011, Australia

If you'd like to get in touch with us, use one of these methods:

General business enquiries: please use this form
All other enquiries: use our support system

BCC Circulation

BCC 7 th Scholarship circulation is published. Please contact http://www.bcc.net.bd

Happy Friendship day

A good friend is like a computer. I 'enter' in your life, 'save' you in my heart, 'format' your problems, 'shift' you to opportunities & never 'delete' you from my memory!

Hypertext Transfer Protocol

Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems.[1] Its use for retrieving inter-linked resources led to the establishment of the World Wide Web.

HTTP development was coordinated by the World Wide Web Consortium and the Internet Engineering Task Force (IETF), culminating in the publication of a series of Requests for Comments (RFCs), most notably RFC 2616 (June 1999), which defines HTTP/1.1, the version of HTTP in common use.

Support for pre-standard HTTP/1.1 based on the then developing RFC 2068 was rapidly adopted by the major browser developers in early 1996. By March 1996, pre-standard HTTP/1.1 was supported in Netscape 2.0, Netscape Navigator Gold 2.01, Mosaic 2.7, Lynx 2.5, and in Internet Explorer 3.0. End user adoption of the new browsers was rapid. In March 1996, one web hosting company reported that over 40% of browsers in use on the Internet were HTTP 1.1 compliant. That same web hosting company reported that by June 1996, 65% of all browsers accessing their servers were HTTP 1.1 Compliant.[2] The HTTP 1.1 standard as defined in RFC 2068 was officially released in January 1997. Improvements and updates to the The HTTP/1.1 standard were released under RFC 2616 in June 1999.

HTTP is a request/response standard of a client and a server. A client is the end-user, the server is the web site. The client making a HTTP request—using a web browser, spider, or other end-user tool—is referred to as the user agent. The responding server—which stores or creates resources such as HTML files and images—is called the origin server. In between the user agent and origin server may be several intermediaries, such as proxies, gateways, and tunnels. HTTP is not constrained to using TCP/IP and its supporting layers, although this is its most popular application on the Internet. Indeed HTTP can be "implemented on top of any other protocol on the Internet, or on other networks." HTTP only presumes a reliable transport; any protocol that provides such guarantees can be used."[3]

Typically, an HTTP client initiates a request. It establishes a Transmission Control Protocol (TCP) connection to a particular port on a host (port 80 by default; see List of TCP and UDP port numbers). An HTTP server listening on that port waits for the client to send a request message. Upon receiving the request, the server sends back a status line, such as "HTTP/1.1 200 OK", and a message of its own, the body of which is perhaps the requested resource, an error message, or some other information.

Resources to be accessed by HTTP are identified using Uniform Resource Identifiers (URIs)—or, more specifically, Uniform Resource Locators (URLs)—using the http: or https URI schemes.

Read More