zoukankan      html  css  js  c++  java
  • The Personal Touch Client Identification 个性化接触 客户识别

    w服务器要知道和谁在交谈。

    HTTP The Definitive Guide

    Web servers may talk to thousands of different clients simultaneously. These servers often need to
    keep track of who they are talking to, rather than treating all requests as coming from anonymous
    clients. This chapter discusses some of the technologies that servers can use to identify who they are
    talking to.

    HTTP began its life as an anonymous, stateless, request/response protocol. A request came from a
    client, was processed by the server, and a response was sent back to the client. Little information was
    available to the web server to determine what user sent the request or to keep track of a sequence of
    requests from the visiting user.
    Modern web sites want to provide a personal touch. They want to know more about users on the other
    ends of the connections and be able to keep track of those users as they browse. Popular online
    shopping sites like Amazon.com personalize their sites for you in several ways:

    Personal greetings

    Welcome messages and page contents are generated specially for the user, to make the
    shopping experience feel more personal.

    Targeted recommendations

    By learning about the interests of the customer, stores can suggest products that they believe
    the customer will appreciate. Stores can also run birthday specials near customers' birthdays
    and other significant days.


    Administrative information on file
    Online shoppers hate having to fill in cumbersome address and credit card forms over and
    over again. Some sites store these administrative details in a database. Once they identify you,
    they can use the administrative information on file, making the shopping experience much
    more convenient.

    Session tracking

    HTTP transactions are stateless. Each request/response happens in isolation. Many web sites
    want to build up incremental state as you interact with the site (for example, filling an online
    shopping cart). To do this, web sites need a way to distinguish HTTP transactions from
    different users.


    This chapter summarizes a few of the techniques used to identify users in HTTP. HTTP itself was not
    born with a rich set of identification features. The early web-site designers (practical folks that they
    were) built their own technologies to identify users. Each technique has its strengths and weaknesses.


    In this chapter, we'll discuss the following mechanisms to identify users:


    HTTP headers that carry information about user identity


    Client IP address tracking, to identify users by their IP addresses


    User login, using authentication to identify users


    Fat URLs, a technique for embedding identity in URLs


    Cookies, a powerful but efficient technique for maintaining persistent identity

  • 相关阅读:
    Git切换分支
    JS中字符串那些事~
    将博客搬至CSDN
    MFC默认窗口类名称
    Windows下使用vim编写代码,使用nmake编译代码,使用vs来调试代码
    从CWnd::GetSafeHwnd实现得到的知识
    ctags使用
    MCI支持的格式在注册表中的位置
    注意!!一定要谨慎使用c/c++原生指针
    MFC模态对话框程序不响应OnIdle
  • 原文地址:https://www.cnblogs.com/rsapaper/p/6396357.html
Copyright © 2011-2022 走看看