thor : “S.F.” title: “Azure动物收养代理和失物招领（译文）” slug: “Azure-Animal-Adoption-Agent-and-Lost-Found” draft: false show_reading_time : true toc: true date: 2020-10-07 12:54:00 +0000 UTC featured_image: “/images/cover.jpg” summary: “基于Azure的宠物收养代理,可帮助宠物爱好者找到理想的宠物,同时挽救小猫和幼犬的生命” description: “基于Azure的宠物收养代理,可帮助宠物爱好者找到理想的宠物,同时挽救小猫和幼犬的生命” Keywords: “Azure,Animal,Adoption,Agent,and,Lost,Found,codeproject” tags: [“C#”,“Windows”,“Mobile”,“Dev”,“Advanced”,“Azure”,“Windows-Phone-7”,“cloud”,".NET4.5",“新闻”,“翻译”]

Azure动物收养代理和失物招领 译文）

原文地址：https://www.codeproject.com/Articles/583225/Azure-Animal-Adoption-Agent-and-Lost-Found

原文作者：roscler

译文由本站翻译

前言

Azure based pet adoption agent that helps pet lovers find the perfect pet while saving the lives of kittens & puppies 基于Azure的宠物收养代理,可帮助宠物爱好者找到理想的宠物,同时挽救小猫和幼犬的生命

• Download ChatEssentials.zip - 12.4 KB下载ChatEssentials.zip-12.4 KB
• Download KittyDar-Photo-Gallery.zip - 621 KB下载KittyDar-Photo-Gallery.zip-621 KB
• Download EnumGenericValueConverter.zip - 2 KB下载EnumGenericValueConverter.zip-2 KB
• **

*NOTE: Learn how to do convenient Two-way data binding to an enumerated property in a Windows Phone app!  (See below after the system architecture diagram).  *

注意:了解如何方便地将双向数据绑定到Windows Phone应用程序中的枚举属性! (请参阅下面的系统架构图).

*(Windows Azure Contest Entry)   *

(Windows Azure竞赛条目)

Table of Contents (目录)

• Phase 1 - Project Overview第一阶段-项目概述
• Phase 2 - Lost & Found Web Site with Cat Face Detector第2阶段-带有猫脸检测器的失物招领网站
• Phase 3 - The Wish List, an SQL Table hosted by Azure阶段3-愿望清单,由Azure托管的SQL表
• Phase 4 - A Virtual Assistant on a Virtual Machine阶段4-虚拟机上的虚拟助手
• Phase 5 - Of Mice and Men阶段5-小鼠和男人

Phase 1 - Project Overview (第一阶段-项目概述)

Why Azure?   (为什么选择Azure？)

*Azure has both software, platform, and infrastructure as a service features, making it the ultimate solution for creating high performance, reliable,  ubiquitous client/server solutions.  The Azure platform eliminates the vast amount of time and cost normally involved in distributed database application development,  allowing a developer like myself to concentrate my time on creating features & value for my users instead of wasting it on support code and infrastructure. *

Azure同时具有软件,平台和基础结构即服务功能,使其成为创建高性能,可靠,无所不在的客户端/服务器解决方案的最终解决方案. Azure平台消除了通常在分布式数据库应用程序开发中涉及的大量时间和成本,使像我这样的开发人员可以将时间集中在为用户创建功能和价值上,而不是将其浪费在支持代码和基础架构上.

*(Note: I already have an Azure account via MSDN)  *

(注意:我已经通过MSDN拥有一个Azure帐户)

Introduction   (介绍)

Azure is the perfect platform for coordinating the search and notification services vital to the creation of a pet adoption agent that connects potential pet owners with the countless adorable kittens & puppies just waiting to give love.  By providing cloud based, easy to configure SQL storage Azure is perfect for storing the search criteria specified by eager pet parents-to-be via the FindAPet client app running on their Windows Phone.  Then Azure Mobile Services is leveraged to send out push notifications to them when pets that meet their stored preferences become available at animal shelters throughout the USA.  The PetFinder API provides ready access to an inventory of adoptable pets of nearly every type and breed and direct access to the animal shelters that house them.  It also provides the necessary animal and shelter search facilities necessary to complete the system, a system that will save the lives of countless innocent loving animals when it’s finished.

Azure是协调搜索和通知服务的理想平台,这对于创建宠物收养代理至关重要,该代理将潜在的宠物主人与数不清的等待爱的可爱小猫和幼犬联系起来.通过提供基于云的,易于配置的SQL存储,Azure非常适合存储渴望的宠物父母通过其Windows Phone上运行的FindAPet客户端应用程序指定的搜索条件.然后,当满足存储要求的宠物在美国的动物收容所中可用时,就可以利用Azure移动服务向他们发送推送通知. PetFinder API提供了对几乎每种类型和品种的可收养宠物清单的直接访问,并可以直接访问容纳它们的动物收容所.它还提供了完成该系统所需的必要的动物和庇护所搜索设施,该系统将在完成后挽救无数无辜爱心动物的生命.

*An auxiliary feature of the system will be a Lost & Found service.  Owners of lost pets can enter a description of the pet they lost.  In a manner similar to Google Alerts, the system will run periodic sweeps of shelters within a 50 mile radius of the owner’s home location.  If a pet matching the owner’s description is found, a push notification will be sent to the owner with a link to the shelter that is holding the pet.  (Thank you Simon Jackson for the Lost & Found idea! ) *

该系统的辅助功能是"失物招领"服务.丢失宠物的主人可以输入丢失宠物的描述.该系统将以类似于Google警报的方式,定期扫描所有者所在位置50英里半径内的避难所.如果找到与主人描述相符的宠物,则会将推送通知发送给主人,并提供指向该宠物住所的链接. (感谢Simon Jackson的失物招领处!)

*Overview *

总览

*The entry point into the system will be the FindAPet app (client) running on the Windows Phone platform using the MVVM Light framework.  It will provide a simple search interface that helps them find the kind of pet they are interested in adopting.  The screens below show a sample session where the user is looking to adopt a Calico kitten: *

系统的入口点将是使用MVVM Light框架在Windows Phone平台上运行的FindAPet应用程序(客户端).它将提供一个简单的搜索界面,可以帮助他们找到他们有兴趣领养的宠物.下面的屏幕显示了一个示例会话,用户正在其中寻求收养印花棉布小猫:

| | |

The system then shows them a list of animal shelters nearby them.  Using the phone’s Geolocation services the user’s current location is used as the center point for a proximity search, as shown in the screenshot below where Boise, Idaho was identified as the the user’s current location.  The user checks off the shelters that they are willing to travel to:

然后,系统向他们显示附近的动物庇护所清单.使用手机的地理位置服务,用户的当前位置被用作邻近搜索的中心点,如下面的屏幕快照所示,其中爱达荷州的博伊西被标识为用户的当前位置.用户检查他们愿意前往的避难所:

The user’s pet and shelter preferences are stored in an Azure hosted SQL table.  As pets at the designated shelters become available, a push notification is sent to the user with the prospective pet’s details and photo for easy viewing.  If they like the pet and are considering adopting it, they can add the pet to their wishlist, as shown in the screen shot below (note an adult cat is shown too since the user selected it in a search where the specified age was adult):

用户的宠物和庇护所首选项存储在Azure托管SQL表中.当指定庇护所的宠物可用时,会向用户发送推送通知以及潜在宠物的详细信息和照片,以方便查看.如果他们喜欢宠物并考虑采用它,则可以将宠物添加到他们的愿望清单中,如以下屏幕截图所示(请注意,由于用户在指定年龄是成年的搜索中选择了成年猫,因此也显示了成年猫) :

*Push notifications will also act as reminders to notify the user when one of the candidate pets is close to their termination date, to make sure they don’t miss the opportunity to save a life while finding a lifelong companion.  Finally, the system will leverage the Nokia Here Maps service to give them directions to the shelter where the chosen pet is at, so they can pick up their new loved one and return home together to share many happy memories.  *

推送通知还可以作为提醒,当其中一只候选宠物接近其终止日期时通知用户,以确保它们在寻找终身伴侣时不会错过挽救生命的机会.最后,该系统将利用Nokia Here Maps服务为他们提供前往所选宠物所在的庇护所的路线,以便他们可以接载新爱的宠物并返回一起回家,分享许多快乐的回忆.

Two-way data binding to an enumerated property without creating new value converters or creating auxiliary properties (MVVM Light)!  (将双向数据绑定到枚举属性,而无需创建新的值转换器或创建辅助属性(MVVM Light)!)

Code Project is about source code and so is this contest so I am including the source code for a helpful utility class that I created while working on the FindAPet Windows Phone client.  I became tired of creating auxiliary properties to provide types that were easy to data bind to, just to expose an enumerated property for binding.  Just as tedious was creating a new value converter for each enumeration type.  The attached source file gives you a class you can drop into your MVVM Light C# project.  The code provides a generic value converter for enumerated types so you can create the binding completely through the use of the Create New Data Binding dialog options without having to add any support code to make it happen.

Code Project与源代码有关,因此本次竞赛也是如此.因此,我将包括我在FindAPet Windows Phone客户端上工作时创建的有用实用程序类的源代码.我已经厌倦了创建辅助属性以提供易于数据绑定的类型,只是公开了枚举的属性进行绑定.就像为每种枚举类型创建新的值转换器一样乏味.随附的源文件为您提供了一个类,您可以将其放入MVVM Light C#项目.该代码为枚举类型提供了通用的值转换器,因此您可以通过使用"创建新数据绑定"对话框选项来完全创建绑定,而无需添加任何支持代码即可实现.

*With this code you now have a value converter for any ViewModel enumerated property that does two-way conversion between the Description attribute strings for the enumerated values and the enumeration constants they represent. This allows you to do two-way data binds to an enumerated property without having to do any plumbing code.  The only thing you have to do is set the Converter field to EnumToDescAttrConverter and put the fully qualified type name for the Enumeration type of the bound property in the ConverterParameter field (see picture below for an example).  If you have trouble determining the correct fully qualified Enum type name, just set a break point in the ConvertBack() method where an Exception will be thrown. Then call System.Reflection.Assembly.GetExecutingAssembly().DefinedTypes.ToList() in the Immediate Window to get a list of all currently defined System types in that execution context.  Find the correct fully qualified type name and paste it into the ConverterParameter field. *

现在,通过此代码,您可以为任何ViewModel枚举属性提供一个值转换器,该属性在枚举值的Description属性字符串与其表示的枚举常量之间进行双向转换.这使您可以进行双向数据绑定到枚举属性,而无需执行任何管道代码.您唯一要做的就是将Converter字段设置为EnumToDescAttrConverter并将绑定属性的Enumeration类型的标准类型名称放入ConverterParameter字段中(示例请参见下图).如果您在确定正确的标准Enum类型名称时遇到麻烦,只需在ConvertBack()方法中设置一个断点即可抛出异常.然后在即时窗口中调用System.Reflection.Assembly.GetExecutingAssembly().DefinedTypes.ToList()以获取该执行上下文中所有当前定义的系统类型的列表.找到正确的标准类型名称并将其粘贴到ConverterParameter字段中.

Here’s how it works.  Whenever the view accesses the bound enumerated property, EnumToDescAttrConverter gets the description attribute for the enum when its Convert() method is called:

运作方式如下.每当视图访问绑定的枚举属性时,EnumToDescAttrConverter都会在调用其Convert()方法时获取枚举的描述属性:

// Consumer wants to convert an enum to a description 
//  attribute string.
public object Convert(
                 object value, 
                 Type targetType, 
                 object parameter, 
                 CultureInfo culture)
{
    // Since we don't know what the correct default 
    //  value should be, a NULL value is unacceptable.
    if (value == null)
        throw new ArgumentNullException(
            "(EnumToDescAttrConverter:Convert) The value is unassigned.");

    Enum e = (Enum)value;

    return e.GetDescription();
}

*This gives list boxes and other view elements a nice human readable string to work with.  Now what happens when the view wants to update  an enumerated property with a new value?  For example, the user makes a List Box selection thus triggering a property set call because the List Box’s SelectedItem property is bound to the enumerated property.  This is where the fully qualified type name entered as the ConverterParameter comes into play.  *

这为列表框和其他视图元素提供了一个易于阅读的字符串.现在,当视图要用新值更新枚举属性时会发生什么？例如,由于列表框的SelectedItem属性绑定到枚举属性,因此用户进行了列表框选择,从而触发了属性集调用.这就是输入完全有效的类型名称作为ConverterParameter的地方.

*The  EnumToDescAttrConverter.ConvertBack() method uses the fully qualified type name passed via the Parameter parameter to create the correctly typed concrete enum value using Reflection.  It then searches the description attributes for that enum type to find the enum value associated with the description given in the value parameter, and returns that enum value. *

EnumToDescAttrConverter.ConvertBack()方法使用通过Parameter参数传递的完全限定类型名称来使用Reflection创建正确键入的具体枚举值.然后搜索该枚举类型的描述属性,以找到与值参数中给定的描述关联的枚举值,并返回该枚举值.

// Convert an enumeration value in Description attribute form back to the appropriate enum value.
public object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture)
{
    // Since we don't know what the correct default value should be, a NULL value is unacceptable.
    if (value == null)
        throw new ArgumentNullException(
        	"(EnumToDescAttrConverter:ConvertBack) The value is unassigned.");

    string strValue = (string)value;

    // Parameter parameter must be set since it must contain the concrete Enum class name.
    if (parameter == null)
        throw new ArgumentNullException(
        	"(EnumToDescAttrConverter:ConvertBack) The Parameter parameter is unassigned.");

    string theEnumClassName = parameter.ToString();

    // Create an instance of the concrete enumeration class from the given class name.
    Enum e = (Enum)System.Reflection.Assembly.GetExecutingAssembly().CreateInstance(theEnumClassName);

    if (e == null)
        throw new ArgumentException(
            "(EnumToDescAttrConverter:ConvertBack) Invalid enumeration class name: " 
            + theEnumClassName
            + ". Set a break point here and call "
            + "System.Reflection.Assembly.GetExecutingAssembly().DefinedTypes.ToList()"
            + " in the immediate window to find the right type.  Put that type into "
            + "the Converter parameter for the data bound element you are working with."
            );

    System.Type theEnumType = e.GetType();

    Enum eRet = null;

    // Now search for the enum value that is associated with the given description.
    foreach (MemberInfo memInfo in theEnumType.GetMembers())
    {
        object[] attrs = memInfo.GetCustomAttributes(typeof(DescriptionAttribute), false);

        if (attrs != null && attrs.Length > 0)
        {
            if (((DescriptionAttribute)attrs[0]).Description == strValue)
            {
                // Ignore the case
                eRet = (Enum)Enum.Parse(theEnumType, memInfo.Name, true);
                break; // Found it.
            }
        }
    } // foreach (MemberInfo memInfo in typeof(TEnum).GetMembers())

    // If the string can not be converted to a valid enum value, throw an
    //  Exception.
    if (eRet == null)
        throw new ArgumentException(
            String.Format("{0} can not be converted to an enum value: ", strValue));

    return eRet;
}

Note: Use the ToDescriptionsList<>() method to conveniently grab the description attributes from an Enum  type to fill a List Box or other similar element.  Put the call to it in the property that returns a list of human friendly strings to the UI element bound to the enumerated property.  (For example, the ItemsSource property of a list box):

注意:使用ToDescriptionsList <>()方法可以方便地从Enum类型中获取描述属性以填充列表框或其他类似元素.将对它的调用放在属性中,该属性将人类友好的字符串列表返回到绑定到枚举属性的UI元素. (例如,清单方块的ItemsSource属性):

public static List<string> ToDescriptionsList<t>()
{
    // GetValues() is not available on Windows Phone.
    // return Enum.GetValues(typeof(T)).Cast<t>();
    List<string> listRet = new List<string>();

    foreach (var x in typeof(T).GetFields())
    {
        Enum e;

        if (x.IsLiteral)
        {
            e = (Enum)x.GetValue(typeof(Enum));

            listRet.Add(e.GetDescription());
        } // if (x.IsLiteral)
    } // foreach()

    return listRet;
}

*Below is the enumerated type that represents the different kinds of animals the PetFinder API can search for.  This is an example of using the Description attribute to tie a human friendly string to an enum value: *

下面是枚举的类型,表示PetFinder API可以搜索的不同动物.这是一个使用Description属性将人类友好的字符串绑定到枚举值的示例:

// Example of an Enumerated type with Description Attributes
   // (barnyard, bird, cat, dog, horse, pig, reptile, smallfurry)
   // List of Animal types the breed list method accepts.
   public enum EnumAnimalType
   {
       [Description("Barnyard")]
       barnyard,
       [Description("Birds")]
       bird,
       [Description("Cats & Kittens")]
       cat,
       [Description("Dogs & Puppies")]
       dog,
       [Description("Horses & Ponies")]
       horse,
       [Description("Pigs")]
       pig,
       [Description("Reptiles")]
       reptile,
       [Description("Other Small & Furry")]
       smallfurry
   }

*Example of a Two-way data binding using the generic converter class, with the fully qualified type name I discovered via the Immediate Windows: *

使用通用转换器类进行双向数据绑定的示例,我通过即时Windows发现了完全限定的类型名称:

Detecting Cat Faces and The Lost & Found Web Site(检测猫脸和失物招领网站)

As mentioned in the project overview, the Azure Animal Adoption Agent will have a Lost & Found component that allows worried owners of missing pets to upload pictures of their loved ones, to help others find them.  The site will also be available to pet shelters so they can scan pictures of pets whose owners live close to the shelter, to see if they have picked up a stray that belongs to one of those owners.  The shelter employee can then contact the pet owner to give them the happy news.

如项目概述中所述,Azure Animal Adoption Agent将具有"失物招领"组件,该组件使失踪宠物的担心主人可以上传其亲人的照片,以帮助其他人找到它们.该站点还将对宠物庇护所开放,以便他们可以扫描主人居住在庇护所附近的宠物的照片,以查看他们是否捡到了属于其中一个主人的流浪狗.然后,庇护所的雇员可以联系宠物主人,向他们发送喜讯.

*Thanks to the KittyDar Cat Detector project, cat owners will have an advantage.  Since KittyDar only detects cat faces if the cat is looking at the camera in a portrait orientation, it can be used to assist cat owners in submitting a photo that is as helpful as possible in identifying their pet.  This stops the owner from uploading a photo that may have sentimental value but isn’t very useful for identifying the cat.  In addition, KittyDar can detect if there are multiple cat faces in the photo.  In that case the owner will be instructed to use a different photo that only has their cat in the shot.  *

感谢KittyDar Cat Detector项目,养猫者将有一个优势.由于KittyDar仅在猫以纵向方向注视相机时才检测到猫的脸,因此它可用于帮助猫主人提交有助于识别其宠物的照片.这样可以阻止所有者上传可能具有感性价值但对识别猫不是很有用的照片.此外,KittyDar可以检测照片中是否有多个猫脸.在这种情况下,将指示所有者使用另一只照片中有猫的照片.

*Here are some example photos from the FindAPet web site that illustrate the benefits of the KittyDar cat face detector.  The red bounding rectangle shown in photos where a cat’s face was detected successfully shows the location of the cat’s face as determined by the detection engine: *

以下是FindAPet网站上的一些示例照片,这些照片说明了KittyDar猫脸检测器的优势.成功检测到猫脸的照片中显示的红色边框显示了检测引擎确定的猫脸位置:

Photo 1 - Single cat face detected.  Photo is suitable for Lost & Found purposes

照片1-检测到单张猫脸.照片适合失物招领处

*Photo 2 - Detection Failed.  Cat’s Face is not Oriented Properly.  Unsuitable for Lost & Found Purposes *

照片2-检测失败.猫的脸没有正确定向.不适合失物招领处

Photo 3 - Detection Succeeded but Too Many Cats.  Unsuitable for Lost & Found Purposes(照片3-检测成功,但猫太多.不适合失物招领处)

WebMatrix 3 - Power Tool for Rapid Web Site Deployment with Azure (WebMatrix 3-使用Azure快速部署网站的强大工具)

Detailed Steps To Reproduce the Lost & Found Photo Gallery with Cat Face Detector(使用猫脸检测器重现失物招领处照片库的详细步骤)

 Step 1 (第1步)

Follow the instructions in this tutorial to get the WebMatrix 3 Photo Gallery template up and running:  (按照本教程中的说明启动并运行WebMatrix 3 Photo Gallery模板:)

WebMatrix 3 Photo Gallery Tutorial (WebMatrix 3图片库教程)

At the time this was written, the error message for an unsuccessful CAPTCHA attempt displays before a CAPTCHA attempt is even made.  To correct this, replace the line in Register.cshtml that says:  (在编写此代码时,甚至在进行CAPTCHA尝试之前,都会显示未成功进行CAPTCHA尝试的错误消息.要更正此问题,请替换Register.cshtml中的行:)

@Html.ValidationSummary("Account creation was not successful. Please correct the errors and try again.", excludeFieldErrors: true, htmlAttributes: null)

with

与

@if(IsPost == true )
{
    @Html.ValidationSummary( "Account creation was not successful. Please correct the errors and try again.", excludeFieldErrors: true, htmlAttributes: null)
}

 Step 2 (第2步)

*At the time this was written, the Photo Gallery template was referencing an old version of JQuery in the site layout file, _SiteLayout.cshtml.  If this is still the case, open that file and replace the line SCRIPT element in the HEAD element that references version 1.8.2 with the following snippet: *

在撰写本文时,Photo Gallery模板正在网站布局文件_SiteLayout.cshtml中引用旧版本的JQuery.如果仍然如此,请打开该文件,并使用以下代码段替换引用版本1.8.2的HEAD元素中的SCRIPT元素行:

<!-- The line below references an old version of jquery and was commented out -->
<!-- <script src="~/Scripts/jquery-1.8.2.min.js"></script>-->
<!-- The line references the newer version of jquery included in the Photo Gallery template -->
<script src="~/Scripts/jquery-2.0.0.min.js"></script>

 Step 3 (第三步)

Publish the Photo Gallery web site to your Azure account and inspect it.  You should now be ready for the real fun.

将图库网站发布到您的Azure帐户并进行检查.您现在应该准备好享受真正的乐趣了.

* Step 3*

第三步

Add the KittyDar Javascript files to your WebMatrix 3 project Scripts folder.  You can find these files in the Scripts folder found in the download attached to this article:

将KittyDar Javascript文件添加到WebMatrix 3项目的Scripts文件夹中.您可以在本文所附下载中的脚本文件夹中找到这些文件:

• kittydar-0.1.0.min.jskittydar-0.1.0.min.js
• kittydar-0.1.6.jskittydar-0.1.6.js
• kittydar-demo.jskittydar-demo.js
• kittydar-detection-worker.jskittydar-detection-worker.js

These files provide the code necessary to detect cat faces in photos and to draw the bounding rectangles  on the photo while detection is taking place and after a detection has succeeded.

这些文件提供了检测照片中的猫脸并在检测期间和成功检测后在照片上绘制边框的必要代码.

* Step 4 *

第4步

* Open the Upload.cshtml web page file in WebMatrix and replace this header element:*

在WebMatrix中打开Upload.cshtml网页文件,并替换以下标头元素:

<h1> Upload Lost Cat Photo </h1>

with

与

<h1>Upload Lost Cat Photo</h1>

<p>
    The photo or your lost cat that you upload will be placed in the
    <a class ="italic" href ="~/View/ @galleryId " title ="@ gallery.Name"> @gallery.Name </a> gallery.
</p>
<p> The photo needs to be a picture of your cat looking at the camera, preferably straight ahead and not looking up, down, or to the side.</p>

@section Head {
    <!-- KittyDar cat face detector script files: https://github.com/harthur/kittydar -->
    <script src ="~/Scripts/kittydar-demo.js"></script>
    <script src ="~/Scripts/kittydar-0.1.6.js"></script>
    <!-- CSS to format and align properly the elements used to show the KittyDar operation
         annotations and result. -->
    <link rel ="stylesheet" href ="kitydar.css"/>   
}

<!-- <img class="large-photo" alt="@Html.AttributeEncode(photo.FileTitle)" id="kittydar-viewer" src="@Href("~/Photo/Thumbnail", photo.Id, new { size="large" })" /> -->
    <div id ="viewer-container">
        <!-- This is where the uploaded cat photo is displayed.  It is also where any bounding rectangles that display the cat face detector's progress and final result are displayed -->
        <div class="kittydar-viewer" id ="kittydar-viewer"></div>
        <div id="viewer">
            <canvas id="preview">
            </canvas>
            <canvas id="annotations">
            </canvas>
        </div>
        <!-- This is where progress messages from the KittyDar detector are displayed as it searches for a cat face in the uploaded picture. -->
        <div class="kittydar-progress" id ="kittydar-progress">(none)</div>
    </div>
    <div id ="detection-result">
        <!-- This is where the result of the detection will be displayed, whether it succeeded or failed. -->
        <div class="kittydar-result" id ="kittydar-result">(none)</div>
    </div>

<script> 
// Run the KittyDar cat detector on this photo
detectFromUrl("@Href( "~/Photo/Thumbnail", photo.Id, new { size="large" })");
</script>

* Now I will add the wish list table to the database.  Click on the findapet_wishlist database row and bring up the SQL Database Design wizard: *

现在,我将愿望清单表添加到数据库中.单击findapet_wishlist数据库行并调出SQL Database Design向导:

* Click on Download a starter project for your SQL database to download the project Azure has prepared for you that will make working on the table remotely from Visual Studio easier.  Run Visual Studio and open the SQLDataProj.sln file.  Then double-click on the file named SQLDatabaseProj.publish.xml found in the Solution Explorer pane.  You will see the screen below: *

单击下载适用于您的SQL数据库的入门项目,以下载Azure为您准备的项目,这将使从Visual Studio远程处理表变得更加容易.运行Visual Studio并打开SQLDataProj.sln文件.然后双击在解决方案资源管理器窗格中找到的名为SQLDatabaseProj.publish.xml的文件.您将看到以下屏幕:

*NOTE:  If you do not have a version of Visual Studio that has the SQL Server Data Tools (SSDT), download and install them now from this web page.   If you do not have the SQL menu option in the top level menu bar in Visual Studio, as shown in the figure below, then you need to download them from that web page.  *

注意:如果您没有带有SQL Server数据工具(SSDT)的Visual Studio版本,请立即从此网页下载并安装它们.如果Visual Studio的顶级菜单栏中没有SQL菜单选项,如下图所示,则需要从该网页下载它们.

* Registering the database as a Data-tier Application and enable database drift detection *

将数据库注册为数据层应用程序并启用数据库漂移检测

*I chose to register the database as a Data-tier Application (DAC) by checking the appropriate box for that.  This makes it much easier to move databases around between servers for load balancing and other useful purposes.   DAC’s are great for simple databases like the wish list database but can be problematic for more complex databases.  This article goes into depth about DAC’s so you can make the decision that is right for you.  Later in this segment of the article, I will talk about SQL Server Data Tools (SSDT) to manage databases.  By checking the Block Publish option I can have SSDT check to see if the structure of the data has drifted from the DAC image of the schema and if so, any attempt to publish from Visual Studio will be blocked with a warning indicating this condition.  This is a useful feature to prevent improper updates or database corruption from occurring if the image of the database on the server does not match what we have in our DAC image in Visual Studio.  Further details on SSDT, DACs, and database drift can be found in this article.  *

通过选择相应的复选框,我选择将数据库注册为数据层应用程序(DAC).这使得在服务器之间移动数据库以实现负载平衡和其他有用目的变得更加容易. DAC非常适合诸如愿望清单数据库之类的简单数据库,但对于较复杂的数据库可能会出现问题. 本文深入探讨了DAC,因此您可以做出以下决定:适合你.在本文的此部分的后面,我将讨论SQL Server数据工具(SSDT)来管理数据库.通过检查``阻止发布'‘选项,我可以让SSDT检查以查看数据结构是否已从架构的DAC映像偏移,如果是这样,则从Visual Studio进行的任何发布尝试都将被阻止,并显示警告指示此情况.如果服务器上数据库的图像与Visual Studio中DAC图像中的图像不匹配,这是一项有用的功能,可以防止发生不正确的更新或数据库损坏.有关SSDT,DAC和数据库漂移的更多详细信息,请参见本文.

*The screen below shows my changes: *

以下屏幕显示了我的更改:

*  IP Address firewall settings *

IP地址防火墙设置

*It is necessary to tell Azure that our current IP address is valid for administering the database.  If you do not set up a firewall rule then anytime you attempt a remote operation like publishing the database, etc. you will see an error like this one: *

必须告诉Azure我们当前的IP地址对于管理数据库有效.如果您未设置防火墙规则,则无论何时尝试进行远程操作(例如发布数据库等),都会看到类似以下错误:

*Fortunately Visual Studio and Azure make it very easy to update the firewall rules to accept your current IP address.   Go back to the Azure management portal and click on Set up Windows Azure firewall rules for this IP address.  You will see the following screen from the Azure management portal (with your actual IP address shown of course):  *

幸运的是,Visual Studio和Azure使更新防火墙规则以接受您当前的IP地址变得非常容易.返回Azure管理门户,然后单击为此IP地址设置Windows Azure防火墙规则.您将从Azure管理门户中看到以下屏幕(当然显示了您的实际IP地址):

*Just click Yes and the firewall rules for you database will be updated to accept your IP address.   *

只需单击``是’',您数据库的防火墙规则将更新为接受您的IP地址.

* Database login settings *

数据库登录设置

*Return to Visual Studio and the Publish Database dialog box.  By clicking on the Edit button in the Publish Database dialog you will open the Connection Properties dialog and can provide the login settings for the database.  Using the dialog shown below, provide the correct user name and password that you set using the Azure management portal: *

返回到Visual Studio和``发布数据库'‘对话框.通过单击发布数据库对话框中的编辑按钮,您将打开连接属性对话框并可以提供数据库的登录设置.使用下面显示的对话框,提供您使用Azure管理门户设置的正确用户名和密码:

*It is a good idea to click the Test Connection button to make sure your login settings and IP firewall settings are proper or not.  Once you have validated them you are ready to publish your database. *

单击测试连接按钮以确保您的登录设置和IP防火墙设置正确与否是个好主意.验证它们之后,就可以发布数据库了.

Click OK to dismiss the results dialog box and then click OK again to dismiss the Connection Properties dialog box.  You will find yourself back at the Publish Database dialog.  Click the Publish button to publish the changes to Azure.  When it’s done, the Data Tools Operations pane should show the following progress and result messages:

单击确定以关闭结果对话框,然后再次单击确定以关闭连接属性对话框.您将回到发布数据库对话框.单击发布按钮以将更改发布到Azure.完成后,数据工具操作窗格应显示以下进度和结果消息:

* Adding Tables, Columns, and Indices *

添加表,列和索引

Now that the wish list table is live in Azure, it is time to add the wish list table, define its fields, and define the indexes for the table.  Important!  Instead of using SSDT for those operations I am going to do something unorthodox and use the Azure management portal for that purpose instead.  I am doing this to show you an important SSDT feature for synchronizing remote and local databases, so please follow along.

现在,愿望清单表已经存在于Azure中,是时候添加愿望清单表,定义其字段并定义该表的索引了.重要!与其使用SSDT进行这些操作,不如我做一些非常规的事情,而是使用Azure管理门户来实现此目的.我这样做是为了向您展示同步远程数据库和本地数据库的重要SSDT功能,因此请继续.

Return to the Azure management portal and select the Design Your SQL Database option underneath the Connect to your Database sub-heading, as shown in the figure below:

返回Azure管理门户并选择连接到数据库''子标题下的设计SQL数据库'‘选项,如下图所示:

*Azure will ask you to login into the database as shown in the figure below.  Enter the user name and password you assigned to the database and login now: *

Azure将要求您登录数据库,如下图所示.输入您分配给数据库的用户名和密码并立即登录:

You will see the database design screen as shown in the figure below:

您将看到数据库设计屏幕,如下图所示:

*Click on New Table to create the main table for the database.  Name the table wishlist.  Then add 6 new columns and make sure they match the definitions shown in the screen below.  Make sure the ID column is marked as being the Primary key and that all fields are marked as required.  *

单击新建表为数据库创建主表.将该表命名为心愿单.然后添加6个新列,并确保它们与下面的屏幕中显示的定义匹配.确保将ID列标记为主键,并且所有字段均标记为必填项.

Your column definitions should look like this now:

您的列定义现在应如下所示:

*The reason for adding the pet_name and shelter_name fields is  to speed up most of the display operations we will do in conjunction with the wish list table.  With those fields present in the table we don’t have to make additional calls to the PetFinder API server to get those items.  Many PetFinder API methods just return the ID elements and you have to make a different method call to get the associated names.  This tactic cuts down on the number of calls we make to the PetFinder API, and that helps to keep us below their API’s rate limits.  *

添加pet_name和housing_name字段的原因是为了加快我们将与愿望清单表一起执行的大多数显示操作.使用表中存在的那些字段,我们不必对PetFinder API服务器进行额外的调用即可获取这些项目.许多PetFinder API方法仅返回ID元素,而您必须进行其他方法调用才能获取关联的名称.这种策略减少了我们对PetFinder API的调用次数,这有助于使我们保持在其API速率限制以下.

Now click on Indexes and Keys to define the those items.  Add two indexes as follows:

现在单击索引和键来定义这些项目.添加两个索引,如下所示:

*1) Click on Add an index.  Add an index named IX_wishlist_user_email that indexes the user_email column. *

1)单击添加索引.添加一个名为IX_wishlist_user_email的索引来索引user_email列.

*2) Click on Add an index again.  Add an index named IX_wishlist_shelter_id that indexes the shelter_id column. *

2)再次单击添加索引.添加一个名为IX_wishlist_shelter_id的索引,该索引为shelter_id列建立索引.

* If you succeeded your screen should now look the one shown below: *

如果成功,您的屏幕现在应如下图所示:

*The user_email column is indexed so we can pull up all the pets for a particular user using their E-mail address as the key.  That allows us to make fast queries to find the set of records that make up one user’s wish list.  The shelter_id column is indexed so we can grab all the animals that belong to one particular shelter across all the user’s wish lists, to make the task that scans for animals that will be put to sleep soon faster and easier to execute.  When you are done click the Save icon to save the changes. *

user_email列已建立索引,因此我们可以使用其电子邮件地址作为密钥为特定用户提取所有宠物.这使我们能够快速查询以查找组成一个用户的愿望清单的记录集.根据庇护所栏的索引,我们可以在所有用户的愿望清单中抓取属于一个特定庇护所的所有动物,从而使扫描动物的任务变得更快,更容易执行.完成后,单击保存图标以保存更改.

* Synchronizing Local and Remote Database Schemas*

同步本地和远程数据库架构

*By changing the remote database schema directly we have created a problem.  The database schema we published from Visual Studio using SSDT was an empty database.  Since the remote database now has a new table with a complete set of columns and indexes, the Azure data schema and our local database schema no longer match.  They are out of sync!  Fortunately SSDT gives us an easy way to synchronize them.  I did this on purpose just so I could show you how to use SSDT to synchronize the two database schemas.  *

通过直接更改远程数据库架构,我们创建了一个问题.我们使用SSDT从Visual Studio发布的数据库架构是一个空数据库.由于远程数据库现在具有包含一组完整的列和索引的新表,因此Azure数据架构与我们的本地数据库架构不再匹配.他们不同步!幸运的是,SSDT给我们提供了一种简单的方式来同步它们.我这样做的目的只是为了向您展示如何使用SSDT同步两个数据库模式.

SSDT can compare two database schemas and report the differences between them.  We are going to do that now.  Click the SQL menu option at the top of the Visual Studio IDE, select Schema Compare, and then New Schema Comparison as shown below:

SSDT可以比较两个数据库模式并报告它们之间的差异.我们现在要这样做.单击Visual Studio IDE顶部的SQL''菜单选项,选择架构比较’',然后选择``新建架构比较’',如下所示:

*This creates a new schema comparison as shown below: *

这将创建一个新的架构比较,如下所示:

Since the Azure database image is newer, due to our recent modifications, we need to designate it as the Source for our comparison.  Click the SQL menu option at the top of the Visual Studio IDE, select Schema Compare, and then Select Source as shown below:*

由于Azure数据库映像是较新的,由于我们最近的修改,我们需要将其指定为源以进行比较.单击Visual Studio IDE顶部的SQL菜单选项,选择Schema Compare,然后选择Source,如下所示:

*Use the Select Source Schema dialog as shown below to choose the Azure database as the source for the comparison: *

使用如下所示的``选择源架构'‘对话框选择Azure数据库作为比较源:

After clicking OK it is time to select the target for our comparison.  We want our current Visual Studio SQL database project be the target, since we want to propagate the changes we made from the remote Azure database to our local database project.  Click the SQL menu option at the top of the Visual Studio IDE, select Schema Compare, and then Select Target as shown below:*

单击确定后,该选择比较对象了.我们希望当前的Visual Studio SQL数据库项目成为目标,因为我们要将从远程Azure数据库所做的更改传播到本地数据库项目.单击Visual Studio IDE顶部的SQL菜单选项,选择Schema Compare,然后选择Target,如下所示:

*Select the Visual Studio SQL database project as the target for the comparison using the Select Target Schema dialog shown below.  Our SQL database project is named SQLDatabaseProj:  *

使用下面显示的``选择目标架构'‘对话框,选择Visual Studio SQL数据库项目作为比较目标.我们的SQL数据库项目名为SQLDatabaseProj:

After clicking OK it is time to do the comparison.  Click the SQL menu option at the top of the Visual Studio IDE, select Schema Compare, and then Compare as shown below: *

单击确定后,该进行比较了.单击Visual Studio IDE顶部的SQL菜单选项,选择Schema Compare,然后比较,如下所示:

*SSDT performs the comparison and shows you the differences between the two schemas as you can see in the figure below.  In the left half of the Results pane are the SQL instructions for creating the wish list table, the fields we added, and the indexes too, since all those instructions are needed to make our local SQL database project look like the remote Azure database.   The right half is blank because our SQL Database project currently only has the database definition and nothing more.  Above the Results pane is the Actions table.  It shows you what actions will be taken when the Update button is clicked.  There is only one row in this table to add the wish list table and its indexes to the target.  The Action checkbox is currently checked because we do want to add the table and its indexes to the local database project.  In more complex scenarios there could be multiple rows of different actions necessary to synchronize the two database schemas.  The Action checkbox allows you to decide which actions you want or don’t want to take during the update.  *

SSDT执行比较,并向您显示两种模式之间的差异,如下图所示.在结果窗格的左半部分是创建心愿单表的SQL指令,我们添加的字段以及索引,因为所有这些指令都是使我们的本地SQL数据库项目看起来像远程Azure数据库所必需的.右半部分为空白,因为我们的SQL数据库项目当前仅具有数据库定义,仅此而已.在结果窗格上方是操作表.它显示了单击更新按钮时将采取的措施.此表中只有一行可将愿望清单表及其索引添加到目标.当前已选中操作''复选框,因为我们确实希望将表及其索引添加到本地数据库项目中.在更复杂的场景中,可能需要多行不同的操作来同步两个数据库模式.您可以通过操作'‘复选框来决定在更新过程中要执行或不想执行的操作.

*Click the Update button.  Visual Studio executes the update and then prompts us to do another Compare to refresh the schema comparison screen.  We do that and the comparison screen changes to look like this:   *

点击``更新'‘按钮. Visual Studio执行更新,然后提示我们执行另一个"比较"以刷新架构比较屏幕.我们这样做,比较屏幕将更改为如下所示:

The screen shows us that we have successfully synchronized the two databases and there are no differences between them.

屏幕显示我们已经成功同步了两个数据库,它们之间没有差异.

Conclusion(结论)

*Azure by itself is a powerful, capable database manager.  But the combination of Azure and Visual Studio provides local and remote database features that make SQL database management robust, professional, and easy.  Not only did we rapidly create the core database, table, columns, and indexes necessary to service the FindAPet wish list feature, but we also created a local Visual Studio project that we can use to help move databases between servers for scaling and other important purposes.  Finally, we used the SSDT toolkit that integrates seamlessly with Visual Studio to synchronize effortlessly our local SQL database project with the structure of the remote database living in the Azure cloud.   SSDT gives you a potent method to manage local and remote databases in a robust way that guards against the dangers of database drift, a phenomenon that frequently creeps into even the most well-managed of database projects. *

Azure本身就是一个功能强大且功能强大的数据库管理器.但是Azure和Visual Studio的结合提供了本地和远程数据库功能,这些功能使SQL数据库管理变得强大,专业和容易.我们不仅快速创建了服务FindAPet愿望清单功能所需的核心数据库,表,列和索引,而且还创建了本地Visual Studio项目,可用于帮助在服务器之间移动数据库以进行扩展和其他重要用途.最后,我们使用了与Visual Studio无缝集成的SSDT工具包,轻松地将我们的本地SQL数据库项目与位于Azure云中的远程数据库的结构进行了同步. SSDT为您提供了一种有效的方法,可以以健壮的方式管理本地和远程数据库,以防止数据库漂移的危险,这种现象经常蔓延到即使是管理最完善的数据库项目中.

NOTE: For an in-depth discussion of the many options and capabilities that SSDT provides for doing a database schema comparison, read this article:

注意:要深入讨论SSDT为进行数据库架构比较而提供的许多选项和功能,请阅读本文:

*How to Use Schema Compare to Compare Different Database Definitions *

如何使用架构比较来比较不同的数据库定义

If you do not have a version of Visual Studio that has the SQL Server Data Tools (SSDT) already in it, download and install them now from this web page.

如果您还没有其中装有SQL Server数据工具(SSDT)的Visual Studio版本,请立即从此网页下载并安装它们.

Phase 4 - A Virtual Assistant on a Virtual Machine (阶段4-虚拟机上的虚拟助手)

Most of your web presence needs can be satisfied by Azure’s web site, worker role and other common services.  But there are times when the only valid solution to offering a service on the web is a virtual machine (VM).  A perfect example of such a time is when you have a standalone program that acts as a server, and a great example of such a program is a Chatbot.  A successful chatbot creates the illusion of conversing with another person, when in reality you are talking to a computer that uses sophisticated pattern matching algorithms to analyze your input and then returns a reasonable response.  In this phase of the contest we will provision an Ubuntu Linux VM on Azure.  We will use that VM to run a chatbot  that explains how to use the web site we created in Phase 2 to our site visitors.

Azure的网站,工作人员角色和其他常用服务可以满足您的大多数Web需求.但是有时候,在Web上提供服务的唯一有效解决方案是虚拟机(VM).一个完美的例子就是当您有一个充当服务器的独立程序时,而此类程序的一个很好的例子就是Chatbot.成功的聊天机器人会产生与他人交谈的幻想,而实际上,您正在与使用复杂的模式匹配算法分析计算机的计算机进行交谈,然后返回合理的响应.在竞赛的这一阶段,我们将在Azure上预配置Ubuntu Linux VM.我们将使用该VM运行一个聊天机器人,该聊天机器人向站点访问者解释如何使用在第二阶段中创建的网站.

*Talk to the Lost & Found ChatBot *

与失物招领处的聊天对话

Why Linux?   (为什么选择Linux？)

The chatterbot I chose to use is ChatScript, a battle-tested and powerful open source implementation written by artificial intelligence expert Bruce Wilcox that has won the Loebner Prize for best chatbot on several occasions and is used by several popular web sites for their virtual assistants.  It’s distributed under a liberal open source license that lets you do pretty much anything you want with it without requiring you to distribute your source code.  In the server document for the software (ChatScript Server Manual.pdf),  there is a crucial paragraph on performance and different operating systems:

我选择使用的聊天机器人是ChatScript,这是由人工智能专家[Bruce Wilcox](http://www. linkedin.com/pub/bruce-wilcox/1/73b/a85)曾多次获得[Loebner Prize](Loebner Prize)(http://www.loebner.net/Prizef/loebner-prize.html)最佳聊天机器人奖,几个流行的网站都将其用作虚拟助手.它是根据自由开放源代码许可证分发的,该许可证可让您执行所需的几乎所有操作,而无需分发源代码.在该软件的服务器文档中(ChatScript服务器手册.pdf),其中有关于性能和不同操作系统的关键段落:

*Since Linux also has a significantly smaller memory footprint than Windows, you can run a Linux ChatScript server on an Azure Extra Small Compute instance!  Given Azure’s courtesy usage levels, this means you essentially get to run your chatbot for free!  If you start to get really heavy levels of usage you can just upgrade your VM to a more powerful compute instance.   One of the beauties of Azure is that it can run a Linux VM as effortlessly as a Windows VM.  (Note: if you really want to use Windows to run ChatScript you can.  It will run fine.  But this article focuses on the solution that gives the best performance, both computationally and economically.)  *

由于Linux的内存占用量明显小于Windows,因此您可以在Azure超小型计算实例上运行Linux ChatScript服务器!鉴于Azure的礼貌使用级别,这意味着您基本上可以免费运行聊天机器人!如果您开始真正大量使用,则可以将VM升级到功能更强大的计算实例. Azure的优点之一是它可以像Windows VM一样轻松地运行Linux VM. (注意:如果您确实想使用Windows运行ChatScript,则可以.它会很好地运行.但是本文重点介绍在计算和经济方面都提供最佳性能的解决方案.)

 Step 1 - Provision the Linux VM (第1步-设置Linux VM)

*Setting up a Linux VM on Azure is easy.  Rather than reinvent the wheel, this tutorial will have you up and going with an Ubuntu 12.0.4 LTS VM in a few minutes.  *

在Azure上设置Linux VM很容易.无需重新努力,本教程可以让您在几分钟之内使用Ubuntu 12.0.4 LTS VM.

*Important notes on following the tutorial!: *

关于本教程的重要说明!:

• *When you get to the screen where you select the SIZE for your VM make sure you select Extra Small (Shared core, 768 MB Memory), instead of the author’s choice of Small.*当您进入为虚拟机选择大小的屏幕时,请确保选择特小(共享核心,768 MB内存)'',而不是作者选择的小’’.
• *You do not need RDP (Remote Desktop Protocol)!*您不需要RDP(远程桌面协议)!

*Just follow the first two parts of the article that shows you how to set up the VM and configure it.  Then come back here when you reach the third part that tells you how to install RDP support.  RDP is a great tool for taking remote control of a Linux box, but it has crucial security implications so it must be configured carefully and it can cause a big increase in your bandwidth consumption.  You do not need RDP at all to successfully manage your VM running ChatScript.  Pay special attention to the helpful tip Part Two of that tutorial has on setting a root password. *

只需按照本文的前两部分(向您展示如何设置和配置VM)进行操作即可.然后,当您到达第三部分时,回到这里,告诉您如何安装RDP支持. RDP是用于远程控制Linux机器的出色工具,但是它具有至关重要的安全意义,因此必须仔细配置它,并且可能导致带宽消耗大量增加.您完全不需要RDP即可成功管理运行ChatScript的VM.请特别注意该教程的第二部分有关设置根密码的有用提示.

 Step 2 - Install BitVise (步骤2-安装BitVise)

A great tool for managing your Linux VM is BitVise, an open source app you can use for SSH sessions and has a Windows style File Explorer for transferring files between your Linux VM and your local PC.  It’s free for non-commercial personal use, otherwise you need to buy a license.  Download and install it now.  You will need it to manage your Linux VM.  However, experienced Linux users will already have their own tools to manage a Linux VM and can skip this step.

BitVise是管理Linux VM的绝佳工具,它是一个可用于SSH会话的开源应用程序,并且具有Windows风格的文件资源管理器,可用于在Linux VM和Linux之间传输文件.您的本地PC.它是免费的,用于非商业个人用途,否则您需要购买许可证. 下载并立即安装.您将需要它来管理Linux VM.但是,经验丰富的Linux用户将已经拥有自己的工具来管理Linux VM,并且可以跳过此步骤.

Now run Bitvise.  The first thing you need to do is configure the Host and User Login Details necessary to connect remotely to your Linux VM, using the Login tab on the initial Bitvise screen.  The Host field should contain the DNS you chose for your VM during the VM tutorial in step one.  The Username and Password fields should contain the user name and password you chose for your VM in the VM Configuration screen during the tutorial.  The Initial Method field should be set to password.  When done, the Bitvise Login dialog should show values similar to those below, but with your particular values of course.  Whether or not you choose to save the password associated with this login as I did is up to you:

现在运行Bitvise.您需要做的第一件事是使用初始Bitvise屏幕上的Login选项卡配置远程连接到Linux VM所需的主机和用户登录详细信息. “主机"字段应包含您在第一步的VM教程中为VM选择的DNS.用户名和密码字段应包含您在教程中的VM Configuration屏幕中为VM选择的用户名和密码.初始方法字段应设置为密码.完成后,” Bitvise登录"对话框应显示与下面类似的值,但当然也包含您的特定值.是否像我一样选择保存与此登录名关联的密码取决于您:

Now click the Login button to connect to your Linux VM.  Once you are connected, Bitvise will automatically open an Xterminal window so you can enter commands via an SSH session, and a File Explorer window so you can manage your files securely with SFTP.

现在,单击"登录"按钮以连接到您的Linux VM.建立连接后,Bitvise将自动打开Xterminal窗口,这样您就可以通过SSH会话输入命令,并通过File Explorer窗口来管理文件SFTP安全地进行.

* Step 3 - Install the Ubuntu 32-bit compatibility package *

第3步-安装Ubuntu 32位兼容软件包

Azure installs a 64-bit version of Ubuntu.  ChatScript comes with a pre-built Linux executable called LinuxChatscript32.  It is a 32-bit program and will not run on a 64-bit VM without some help.    Switch to the Xterminal window that Bitvise opened for you automatically and enter this command:

Azure将安装64位版本的Ubuntu. ChatScript带有一个预构建的Linux可执行文件,称为LinuxChatscript32.这是一个32位程序,如果没有一些帮助将无法在64位VM上运行.自动切换到Bitvise为您打开的Xterminal窗口,然后输入以下命令:

*sudo apt-get install ia32-libs *

须藤apt-get install ia32-libs

 ( )

*Enter your superuser password as required by the sudo command.  After answering the confirmation prompt, it will take about 5 to 10 minutes for the library to be installed.  When it’s done your VM is now ready to run 32-bit programs like ChatScript. *

根据sudo命令的要求输入超级用户密码.回答确认提示后,大约需要5到10分钟才能安装库.完成后,您的VM现在可以运行诸如ChatScript之类的32位程序了.

 Step 4 - Download ChatScript (步骤4-下载ChatScript)

 ( )

*Download ChatScript and extract the contents of the compressed archive to a directory of your choosing on your local PC.  That directory will be your local install directory.  *

下载ChatScript,然后将压缩存档的内容提取到本地PC上您选择的目录中.该目录将是您的本地安装目录.

 Step 5 - Transfer ChatScript to the Linux VM(第5步-将ChatScript传输到Linux VM)

Switch to the File Explorer window Bitvise opened for you.  The left pane (Local Files) contains your local PC files and the right pane (Remote Files) contains the files on the Ubuntu instance running in a VM.  In the Local Files pane, navigate to the directory that contains the extracted contents of the ChatScript 3.1 zip file.  Then navigate to the parent of that directory so you can see the top level ChatScript directory.  The Remote Files pane should already be set to the top level directory for the user you configured to manage the VM.  Drag the ChatScript directory from Local Files over to Remote Files so that the entire file structure is replicated into the Ubuntu instance:

切换到"文件资源管理器"窗口Bitvise为您打开.左窗格(本地文件)包含本地PC文件,右窗格(远程文件)包含在VM中运行的Ubuntu实例上的文件.在"本地文件"窗格中,导航到包含ChatScript 3.1 zip文件的提取内容的目录.然后导航到该目录的父目录,以便您可以看到顶级ChatScript目录.对于配置为管理VM的用户,“远程文件"窗格应已设置为顶级目录.将ChatScript目录从本地文件拖到远程文件,以便将整个文件结构复制到Ubuntu实例中:

Once you have done this, Bitvise will begin the file transfer and display a message in the status bar that says “Preparing upload list..” for a few minutes.  Then it will display the ongoing status of the transfer.  With my ISP the transfer took about 22 minutes so get a sandwich or write another article for Code Project while you wait for it to complete:

完成此操作后,Bitvise将开始文件传输,并在状态栏中显示"准备上传列表..“的消息,并持续几分钟.然后它将显示正在进行的传输状态.使用我的ISP进行传输大约需要22分钟,因此在等待完成之前,请拿一份三明治或为Code Project写另一篇文章:

 ( )

Once the file transfer has completed, you need to tell Linux that the file named LinuxChatscript32 is an executable program, by setting its file permissions as follows:

文件传输完成后,您需要通过如下设置其文件权限来告知Linux名为LinuxChatscript32的文件是可执行程序:

• *Navigate into the ChatScript sub-directory that should now be visible in the Remote Files pane by double-clicking on it.*双击进入ChatScript子目录,该目录现在应该在``远程文件'‘窗格中可见.
• *Find the file named LinuxChatscript32.*找到名为LinuxChatscript32的文件.
• *Right-click on it and choose Properties from the pop-up menu.*右键单击它,然后从弹出菜单中选择属性.
• *Select the Permissions tab.*选择权限选项卡.
• *Make sure you have checked the boxes so that the permissions for LinuxChatscript32 match those in the screen below:*确保已选中复选框,以使LinuxChatscript32的权限与以下屏幕中的权限匹配:

The ChatScript server is now ready to run.

ChatScript服务器现在可以运行了.

 Step 6 - Making ChatScript Robust (第6步-使ChatScript健壮)

You want the ChatScript server to be up and running at all times, or close to it.  If it crashes, you want the Linux VM to automatically restart it without requiring your intervention.  Linux has a background process called cron that is used to launch background tasks at predetermined times and is installed by default in an Azure Ubuntu Linux VM.   To accomplish this goal we make an entry into the cron table that tells the Linux VM to launch ChatScript every 5 minutes.  ChatScript will simply exit if the port it uses to listen for connections is already opened.  Therefore, if ChatScript has crashed then it will be reloaded when cron launches it at the next 5 minute interval.  If it is already running then ChatScript simply exits.  The net result is an automated method that keeps our ChatScript running nearly all the time.  If ChatScript crashes then at most we will be without its services for 5 minutes or less.

您希望ChatScript服务器始终处于启动状态或在附近运行.如果崩溃,您希望Linux VM在不需要干预的情况下自动重启它. Linux具有称为cron的后台进程,该进程用于在预定时间启动后台任务,默认情况下安装在Azure Ubuntu Linux VM中.为了实现此目标,我们进入cron表,该表告诉Linux VM每5分钟启动一次ChatScript.如果用于监听连接的端口已打开,则ChatScript只会退出.因此,如果ChatScript崩溃了,则当cron每隔5分钟启动它时,它将重新加载.如果它已经在运行,那么ChatScript只会退出.最终结果是一种自动化的方法,可使我们的ChatScript几乎始终保持运行状态.如果ChatScript崩溃,那么最多5分钟或更短时间内我们将无法使用它.

Here’s how to make the cron table entry that does this.  Switch to the Xterminal window again.  At the prompt enter:

这是制作执行此操作的cron表条目的方法.再次切换到Xterminal窗口.在提示符下输入:

crontab -e

crontab -e

*Then do the following: *

然后执行以下操作:

• *Accept the default choice of Nano as the editor to use for editing the cron table.*接受默认的Nano选项作为编辑器,用于编辑cron表.
• *Copy the line below to the clipboard, followed by right-clicking on the Xterminal system icon in the upper left hand corner, and then choosing Edit -> Paste:*将以下行复制到剪贴板,然后右键单击左上角的Xterminal系统图标,然后选择"编辑”->“粘贴”:

*0,5,10,15,20,25,30,35,40,45,50,55 * * * * cd /home/[username]/ChatScript; ./LinuxChatscript32 2>/home/[username]/cronserver.log *

0,5,10,15,20,25,30,35,40,45,50,55 * * * * cd/home/[用户名]/ChatScript; ./LinuxChatscript32 2>/home/[用户名]/cronserver.log

• *Replace [username] with the user name you assigned to VM Configuration dialog during the Linux VM tutorial.*将[username]替换为您在Linux VM教程中分配给VM Configuration对话框的用户名.
• *Now type Ctrl-X to save the file.*现在,按Ctrl-X保存文件.
• Type Y to accept the save输入Y接受保存
• *Click Enter to accept the crontab file name offered to you.*单击Enter接受提供给您的crontab文件名.

You will see a status message telling you that the cron table has been installed.  Now, every five minutes cron will change to the top level directory for ChatScript, and execute LinuxChatscript32, the program that is the ChatScript server.  Any errors that occur during the attempt will be written to the cronserver.log file in the given directory.  You can easily see the contents of your cron table with the following command, which will dump the current contents of the cron table to the screen (note, the character after the dash is a lowercase “L”):

您将看到一条状态消息,告诉您cron表已安装.现在,cron将每隔五分钟切换到ChatScript的顶级目录,并执行作为ChatScript服务器的程序LinuxChatscript32.尝试期间发生的任何错误都将写入给定目录中的cronserver.log文件.您可以使用以下命令轻松地查看cron表的内容,该命令会将cron表的当前内容转储到屏幕上(请注意,破折号后的字符为小写” L"):

*crontab -l  *

crontab -l

*To look at the contents of the cronserver.log file,  go to the top level directory for ChatScript while inside the Xterminal window and enter the following command: *

要查看cronserver.log文件的内容,请在Xterminal窗口中转到ChatScript的顶级目录,然后输入以下命令:

*cat cronserver.log *

猫cronserver.log

*That will dump the contents of the log file to the screen.  You can easily test to see if your cron table entry is working by waiting 5 minutes, and then executing the following command in the Xterminal window: *

这会将日志文件的内容转储到屏幕上.通过等待5分钟,然后在Xterminal窗口中执行以下命令,可以轻松地测试您的cron表条目是否正常工作:

*netstat –listen  *

netstat-听

*This command will show you all the ports that running processes are listening on.  You should see that port 1024 is in use.  If not, recheck carefully your steps during the cron table editing operation above for errors, especially for typos in any path entries.  You can also look at the file /home/[username]/cronserver.log and see if any errors occurred during the cron job.  (Note: ChatScript listens on port 1024 by default, but you can change that if you like via the configuration files.  See the ChatScript server manual for details).    *

此命令将显示正在运行的进程正在侦听的所有端口.您应该看到端口1024正在使用中.如果不是,请在上面的cron表编辑操作期间仔细检查您的步骤是否有错误,尤其是任何路径条目中的错别字.您还可以查看文件/home/[用户名]/cronserver.log并查看在cron作业期间是否发生任何错误. (注意:默认情况下,ChatScript在端口1024上侦听,但是如果您愿意,可以通过配置文件进行更改.有关详细信息,请参阅< ChatScript服务器手册>).

 Step 7 - Making ChatScript Available to the Web (步骤7-使ChatScript可用于Web)

We need to tell Azure to route traffic from the Web to the internal port that ChatScript is listening on.  This is done by setting up an Endpoint with the help of the Azure Management Portal.  Follow these steps now:

我们需要告诉Azure将流量从Web路由到ChatScript正在侦听的内部端口.这是通过在Azure管理门户的帮助下设置一个端点来完成的.立即执行以下步骤:

• Log into the Azure Management Portal登录到Azure管理门户
• When the portal is fully ready, click on the Virtual Machines icon门户完全准备就绪后,单击"虚拟机"图标
• Select the Ubuntu Linux VM you created from the list从列表中选择您创建的Ubuntu Linux VM
• Click on the ENDPOINTS option to see the current list of Endpoints单击ENDPOINTS选项,以查看当前的端点列表
• Click on the ADD  button to add a new Endpoint单击添加按钮以添加新的端点
• *Accept the default ADD ENDPOINT option as shown in the figure below by clicking on the right-facing arrow that takes you to the next step:*通过单击将您带到下一步的向右箭头,接受下图所示的默认ADD ENDPOINT选项:

In the dialog that appears, give the new Endpoint the name ChatScript while keeping the default value of TCP for the protocol. Set both the PUBLIC PORT and PRIVATE PORT fields to 1024. the port that ChatScript listens on for new connections.  Your screen should like like the figure below:*

在出现的对话框中,为新的端点命名(ChatScript),同时保留协议的TCP默认值.将PUBLIC PORT和PRIVATE PORT字段都设置为1024.ChatScript侦听新连接的端口.您的屏幕应如下图所示:

*Click on the checkmark icon to go to the next step.   You will see a status message saying UPDATE IN PROGRESS while Azure adds your new endpoint.  This will take a few minutes.  When it is done your Endpoint list screen should look like the following: *

单击复选标记图标转到下一步.当Azure添加新端点时,您将看到一条状态消息,显示"正在进行中更新".这将需要几分钟.完成后,“端点列表"屏幕应如下所示:

 Step 8 - Restricting Access to ChatScript’s Meta-Commands (步骤8-限制对ChatScript的元命令的访问)

ChatScript has commands that can be issued remotely to the server, directly from a chat.  They all start with a colon (":") and they usually have a dramatic affect on the ChatScript server such as completely reloading it, adding new content, and more.  They should only be used by you or someone you designate as a system administrator. They absolutely should not be available to everyone that visits your chatbot!

ChatScript具有可以直接从聊天远程发布到服务器的命令.它们全都以冒号(":")开头,并且通常会对ChatScript服务器产生巨大影响,例如完全重新加载它,添加新内容等等.它们仅应由您或您指定为系统管理员的人员使用.绝对不应该对访问您的聊天机器人的所有人开放!

There is a file in the top level ChatScript directory called authorizedIP.txt.  This file should be edited to contain only the IP addresses that should be allowed to issue meta-commands.  The file ships with the word “all” as its sole contents which is dangerous.  While at the PC that you will use to administrate the ChatScript server, visit a site like What Is My IP to discover your IP address, and enter that into the authorizedIP.txt file.  Repeat this procedure for each PC you want to grant access to, if they are at different IP addresses.  You can use the Nano editor to edit the file, the same editor you used to edit the cron table.  To perform the edit, switch to the Xterminal window, make sure you are in the top level ChatScript directory, and use the following command:

顶级ChatScript目录中有一个文件,名为authorizedIP.txt.该文件应被编辑为仅包含应允许发出元命令的IP地址.该文件的唯一内容是单词” all",这很危险.在用于管理ChatScript服务器的PC上,访问我的IP是什么之类的站点以找到您的IP地址,并将其输入到授权IP.txt中文件.如果您要授予访问权限的每台PC位于不同的IP地址,请对其重复此过程.您可以使用Nano编辑器编辑文件,该文件与用于编辑cron表的编辑器相同.要执行编辑,请切换到Xterminal窗口,确保您位于顶级ChatScript目录中,并使用以下命令:

*nano authorizedIP.txt *

纳米授权IP.txt

Make sure you delete the “all” keyword first.

确保首先删除" all"关键字.

 Step 9 - Wrapping the ChatScript TCP Request in an HTTP GET request (步骤9-将ChatScript TCP请求包装在HTTP GET请求中)

*The ChatScript server does not respond to HTTP requests, it only accepts TCP socket connections on the port it is listening on.  Although ASP.NET web sites can open sockets directly, it is much more convenient to use AJAX requests, especially when it comes to crafting a nice web page that interacts with the user while proxying the ChatScript server behind the scenes.  Unfortunately due to browser security restrictions on Javascript AJAX requests only work with HTTP requests.  The trick then is to create a web page that can accept an HTTP GET request, make the TCP connection to the ChatScript server, issue the chat request using the given GET parameters, and return the server’s response as a typical response page.  That is precisely what the file ChatRelay.cshtml does.     *

ChatScript服务器不响应HTTP请求,它仅在其侦听的端口上接受TCP套接字连接.尽管ASP.NET网站可以直接打开套接字,但使用AJAX请求要方便得多,尤其是在制作一个漂亮的网页时,该网页与用户交互,同时在后台代理ChatScript服务器.不幸的是,由于浏览器对Javascript的安全性限制,AJAX请求仅适用于HTTP请求.然后,诀窍是创建一个网页,该网页可以接受HTTP GET请求,建立与ChatScript服务器的TCP连接,使用给定的GET参数发出聊天请求,并以典型的响应页面形式返回服务器的响应.这正是ChatRelay.cshtml文件的作用.

*A client request to the ChatScript server consists of sending 3 null terminated strings to the server.  Here’s the code from ChatMessage.cs that shows the properties for the class ChatMessage that embodies a ChatScript server request.  :   *

向ChatScript服务器发送的客户端请求包括向服务器发送3个以null终止的字符串.这是ChatMessage.cs中的代码,显示了体现ChatScript服务器请求的类ChatMessage的属性. :

public class ChatMessage
{
    public static string NULL_TERMINATOR = "\0";

    public string LoginName { get; set; }
    public string BotName { get; set; }
    public string Message { get; set; }

    ...
} // public class ChatMessage 

*The LoginName is the unique ID you assign to the user.  This is necessary so that the chatbot can remember information for a particular user between sessions.  That is, between separate visits by a user to the chatbot web page.  The BotName is the name of the bot to use.  ChatScript can support multiple chatbots, each with their own “personalities”, fact sets, and conversation rules.  It can be left empty to use the default chatbot.  The Message is the text the user entered that requires a response from the chatbot.  *

LoginName是您分配给用户的唯一ID.这是必要的,以便聊天机器人可以在会话之间记住特定用户的信息.也就是说,在用户分别访问聊天机器人网页之间. BotName是要使用的机器人的名称. ChatScript可以支持多个聊天机器人,每个聊天机器人都有自己的"个性",事实集和对话规则.可以将其保留为空以使用默认的聊天机器人.消息是用户输入的文本,需要聊天机器人的响应.

*Along with other helpful methods the ChatMessage class contains ToString().  This method builds a string that you can send directly to the chat server with the chat message properties properly formatted with C string NULL terminator characters: *

ChatMessage类与其他有用的方法一起包含ToString().此方法生成一个字符串,您可以使用正确的C字符串NULL终止符格式将聊天消息属性直接发送到聊天服务器:

/// <summary>
//  Returns a string formatted properly for acceptance by the ChatScript server.
/// </summary>
/// <returns></returns>
public override string ToString()
{
    // The ChatScript server expects 3 C-style strings terminated with the null terminate character.  Ascii(0)
    //  The 3 strings are the login name (user ID), the chatbot name, and the last message from a current
    //  conversation, or an empty string if this is the first message for a new session, where a session is
    //  defined as the user "entering" the web page to chat with the chat bot.
    return this.LoginName + NULL_TERMINATOR + this.BotName + NULL_TERMINATOR + this.Message + NULL_TERMINATOR;
} // public string ToString()

*This class also contains a handy method name readChatScriptMessage() that reads the response from the ChatScript server from an open socket connection and returns it as a string.  The ChatMessage class is utilized by ChatRelay.cshtml to talk to the ChatScript server.   ChatRelay.cshtml takes 3 GET request arguments that correspond directly to the 3 properties in the ChatMessage class, and have the exact same name for simplicity.  Here’s a sample GET request using the FindAPet web site: *

此类还包含一个方便的方法名称readChatScriptMessage(),该方法从打开的套接字连接中读取ChatScript服务器的响应并将其作为字符串返回. ChatRelay.cshtml使用ChatMessage类与ChatScript服务器对话. ChatRelay.cshtml接受3个GET请求参数,它们直接与ChatMessage类中的3个属性相对应,并且为简单起见具有完全相同的名称.这是使用FindAPet网站的示例GET请求:

http://findapet.azurewebsites.net/Chat/ChatRelay.cshtml?LoginName=192_58_16_17&BotName=&Message=I%20lost%20my%20cat.%20%20Can%20you%20help%20me?

http://findapet.azurewebsites.net/Chat/ChatRelay.cshtml?LoginName=192_58_16_17&BotName=&Message=I%20lost%20my%20cat.%20%20Can%20you%20help%20me？

This request tells ChatRelay.cshtml to ask the chatbot the question"I lost my cat.  Can you help me?".  Currently the user’s IP address with periods being substituted by underscores is used as their ID.  This is a flawed approach since they could be sharing the IP address or have a dynamic IP address, but it makes it easy to deal with guest users.  The risk is that information memorized by the chatbot will be mixed between people using the same IP address, or lost if a user revisits the web site with a new IP address, but for now it’s a quick and dirty solution for easy guest visitor access.  A better solution would be a cookie based approach but that fails too if they block or reject cookies.  The best solution is requiring a user account with a verified E-mail address, but that would require that they create an account just to interact with the chatbot.  Pick your poison and run with whatever approach suits your web site the best.

该请求告诉ChatRelay.cshtml向聊天机器人询问以下问题:“我失去了猫.您能帮我吗？".当前,使用用户的IP地址(用下划线代替句点)作为其ID.这是一种有缺陷的方法,因为他们可以共享IP地址或拥有动态IP地址,但是它使与来宾用户的交往变得容易.风险是,聊天机器人存储的信息将在使用相同IP地址的人们之间混合,或者如果用户使用新IP地址重新访问该网站,则该信息将丢失,但是目前,这是一种快速而又肮脏的解决方案,可方便访客访问.更好的解决方案是基于cookie的方法,但是如果它们阻止或拒绝cookie,也会失败.最好的解决方案是要求用户帐户具有经过验证的电子邮件地址,但这将要求他们创建一个帐户以便与聊天机器人进行交互.选择您的毒药并以最适合您的网站的任何方式运行.

*The first thing ChatRelay.cshtml does is get the IP address for the Linux VM so we can use it to open a socket connection.  (Note: instead of [azuredns] you would put the DNS name you assigned to your Linux VM when you created it): *

ChatRelay.cshtml的第一件事是获取Linux VM的IP地址,因此我们可以使用它来打开套接字连接. (注意:您可以创建Linux VM时分配给您的DNS名称而不是[azuredns]):

// Lookup the IP address for our chatscript server. (Cache this value
//  in a later build since GetHostEntry() is reportedly a slow call.)
IPAddress ipAddress = Dns.GetHostEntry("[azuredns].cloudapp.net").AddressList[0];

*Then the URL arguments from the GET request are validated.  The LoginName is required, but the BotName and Message arguments are not.  Note, checkForValidURLArgument() is a simple method that validates a URL parameter and throws an Exception if it is invalid and the parameter is one that is marked as required.  You will find it and several other helper methods in ChatRelay.cshtml:  *

然后,验证来自GET请求的URL参数.登录名是必需的,但BotName和Message的参数不是必需的.注意,checkForValidURLArgument()是一种简单的方法,该方法可验证URL参数,并在该参数无效且参数是标记为必需的参数时引发Exception.您可以在ChatRelay.cshtml中找到它和其他几个帮助方法:

// LoginName, is mandatory.
strLoginName = checkForValidURLArgument("LoginName", true);

// BotName, is optional.
strBotName = checkForValidURLArgument("BotName", false);

// User message (chatbot input), is optional.  But remember,
//  only send a blank message to start a new session
//  with ChatScript!  After that, send the user's input
//  each time.
strMessage = checkForValidURLArgument("Message", false);

Once the parameters are validated, it is time to connect to the ChatScript server, create a chat message object using the given GET request parameters, send the request to the chatbot, and wait for a response:

一旦参数经过验证,就可以连接到ChatScript服务器,使用给定的GET请求参数创建聊天消息对象,将请求发送到聊天机器人,然后等待响应:

// Connect to the ChatScript server.
TcpClient tcpCli = new TcpClient();
tcpCli.Connect(ipAddress, 1024);

// Open the stream
streamChatScript = tcpCli.GetStream();
StreamReader sr = new StreamReader(streamChatScript);
BinaryWriter sw = new BinaryWriter(streamChatScript);

// Create a message to send to the server, using the URL argument values
//  passed to us.
ChatMessage cm = new ChatMessage(strLoginName, strBotName, strMessage);

// Send the message to the chat server.
string strSendChatMsg = cm.ToString();

// Translate the passed message into ASCII and store it as a Byte array.
Byte[] data = System.Text.Encoding.ASCII.GetBytes(strSendChatMsg);

for (int i = 0; i < strSendChatMsg.Length; i++)
{
    data[i] = (byte)strSendChatMsg[i];
}

// Send the chat message.
streamChatScript.Write(data, 0, data.Length);

strResponseMsg = ChatMessage.readChatScriptMessage(streamChatScript);

The guts of the web page simply displays the response, wrapped XML style in a tag named response by the formatResponse() method:

网页的内容只是通过formatResponse()方法在名为response的标记中显示响应,包装的XML样式:

<html lang="en">
    <head>
        <meta charset="utf-8" />
        <title></title>
    </head>
    <body>
    <!-- Just output the response message from the C# code above -->    
    @strResponseMsg
    </body>
</html>

*A sample response from the ChatScript server, returned inside the rendered web page could look like:  *

来自ChatScript服务器的示例响应,在呈现的网页内返回,如下所示:

<response>Do you have a photo of your cat?</response>

*Remember, the user never sees this output.  Only the web page that the interacts with the user and makes a behind the scenes AJAX request to ChatRelay.cshtml sees it, as described below. *

请记住,用户永远不会看到此输出.如下所述,只有与用户交互并向ChatRelay.cshtml发出后台AJAX请求的网页才能看到它.

 Step 10 - Chatting with the User (第10步-与用户聊天)

The page that interacts with the user is called Chat/Default.cshtml.  You can use it as a starting point for your own web site.  With a few small modifications you should be good to go.  It’s time to explain how the web page that interacts with the user and the ChatScript server works.   You can talk to the Lost & Found ChatBot now using the link below:

与用户交互的页面称为Chat/Default.cshtml.您可以将其用作自己的网站的起点.进行一些小的修改,您应该就很好了.现在是时候解释与用户和ChatScript服务器交互的网页如何工作了.您现在可以使用以下链接与"失物招领"聊天室进行交谈:

 Talk to the Lost & Found ChatBot   (与失物招领聊天室交谈)

*Below is a screenshot of the chat page: *

以下是聊天页面的屏幕截图:

*This is the web page named Chat/Default.cshtml.  The active elements that comprise the web page are contained within the DIV that has the ID “#q_and_a”.  It contains a text area with the ID of “#entry”, a submit button with the ID “#do_chat”, a DIV with the ID “#user_question” and another DIV with the ID “chat_response”: *

这是名为Chat/Default.cshtml的网页.构成网页的活动元素包含在ID为” #q_and_a"的DIV中.它包含一个ID为" #entry"的文本区域,一个ID为" #do_chat"的提交按钮,一个ID为" #user_question"的DIV和另一个ID为" chat_response"的DIV:

    <div id="q_and_a" >
    <br />
    <div id="user_input" class="q_and_a_element" >
        <h3 class="label">Enter your question or reply in the box below.</h3>
        <textarea id="entry" onkeypress="if(event.keyCode==13) return doChat();" rows="2" cols="" name="entry"></textarea>
        <br>
        <input type="button" value="Ask" id="do_chat" name="do_chat" onclick="doChat()" >
    </div>
    <div id="you_said" class="q_and_a_element" >
        <div class="label">You said:</div>
        <div id="user_question" class="q_and_a_text_field" >
            <!-- When the user hits the submit button, their question will be echoed here. -->
            &nbsp;
        </div>
    </div>
    <div id="i_replied" class="q_and_a_element" >
        <div class="label">I said:</div>
        <div id="chat_response" class="q_and_a_text_field" >
            <!-- When the user hits the submit button, the response from the ChatScript server will be placed here. -->
            &nbsp;
        </div>
    </div>
</div>

*A small piece of JQuery Javascript adds a document ready event handler that calls the Javascript method doChat() with the bFirstMessage parameter set to TRUE.  As described previously, this sends a chat request to the ChatScript server with an empty Message field, the only time this happens during a chat session.  This lets the chatbot know that this is the start of a new session or conversation with the current user: *

一小段JQuery Javascript添加了一个文档就绪事件处理程序,该事件处理程序调用bFirstMessage参数设置为TRUE的Javascript方法doChat().如前所述,这会将聊天请求发送到带有空Message字段的ChatScript服务器,这是在聊天会话期间唯一的时间.这使聊天机器人知道这是与当前用户的新会话或对话的开始:

<script>
    // When the page is loaded, send a chat with an empty message to let the ChatScript
    //  server know this is a new session for the current user.
    $(document).ready(function () 
    {
        // Set the bFirstMessage parameter to TRUE so the chatbot knows this is the start of a new session.
        doChat(true);
    });
</script>

*The chat session is now in progress and from this point on the following pattern repeats until the user leaves the chat page.  The user enters their question or response in the “#entry” textarea and then hits the Enter key or clicks the Ask button.  This triggers a call to the method doChat() that does all the work.  In this case bFirstMessage is omitted resulting in that parameter being set to FALSE.  If the user neglected to enter anything into the “#entry” textarea, an alert box will pop up telling the user to enter something and the chat request will be not be submitted: *

聊天会话现在正在进行中,从这一点开始,以下模式将重复进行,直到用户离开聊天页面为止.用户在``#entry'‘文本区域中输入他们的问题或答案,然后按Enter键或单击Ask按钮.这会触发对方法doChat()的调用,该方法可以完成所有工作.在这种情况下,bFirstMessage被省略,导致该参数设置为FALSE.如果用户忽略了在" #entry"文本区域中输入任何内容,则会弹出一个警告框,告诉用户输入内容,并且聊天请求不会被提交:

// This method is called when the user hits the ASK button.  The user's current message
//  is sent to the ChatScript server and the server's response is shown in the "You said"
//  DIV element.
//
// PARAMETERS:
//  bFirstMessage - If TRUE then an empty message is sent to the ChatScript server to
//   let it know this is a new chat session for this user.  If FALSE, then an empty
//   message will trigger an alert telling the user to enter a valid message.
function doChat(bFirstMessage)
{

    // The default value for bFirstMessage is FALSE.
    typeof bFirstMessage == 'undefined' ? false : bFirstMessage;

    var strGuestID = "@strGuestID";
    var strMessage = "";

    if (bFirstMessage)
    {
        // First message.  Send an empty message but show the word "Hello"
        //  as the user's question.
        $("#user_question").html("Hello.");
    }
    else
    {
        // Not first message.  Look for the user message in the message entry text area.
        strMessage = $("#entry").val().trim();

        // Empty messages are not allowed if this is not the first message
        //  for the session..
        if ((!bFirstMessage) && (strMessage.length < 1))
        {
            alert("Please enter a question or statement first.");
            return;
        }

        // Show the question.
        $("#user_question").html(strMessage);
    } // else - if (bFirstMessage)

    // Build the URL and URL arguments to make the request to the ChatScript server
    //  via the ChatRelay page.
    var strUrl =
        "/Chat/ChatRelay.cshtml"
        + "?"
        + "LoginName=" + encodeURI(strGuestID)
        + "&"
        + "BotName=" + encodeURI("")
        + "&"
        + "Message=" + encodeURI(strMessage);

    $.ajax(
        {
            url: strUrl,
            // Do not cache the results of a query.  We want a fresh response
            //  from the ChatScript server each time.
            cache: false
        }).done(function (html) {
            var strResponse = "(none)";

            // Wipe the text area of the user's last question so they can enter something new.
            $("#entry").val("");

            // Extract the response contained in our "response" XML tags.
            var re = /&lt;response&gt;(.*?)&lt;\/response&gt;/im;
            var match = re.exec(html);

            if (match != null) {
                strResponse = match[1].trim();
            }
            else {
                strResponse = "Chat is offline at the moment.  Please try again in 30 minutes.";
            } // else if (match != null)

            // Show the response returned by the ChatScript server.
            // $("#chat_response").val(strResponse);
            $("#chat_response").html(strResponse);

        });
} // function doChat()

The first thing doChat() does is build the GET request with the proper URL arguments to send to the chatbot:

doChat()首先要做的是使用适当的URL参数构建GET请求以发送到聊天机器人:

• *LoginName is set to the user’s IP address properly formatted.*LoginName设置为正确设置的用户IP地址.
• *BotName is left empty since we are using the default chatbot.*由于我们使用的是默认聊天机器人,因此BotName保留为空.
• Message is set to the text just entered by the user消息设置为用户刚输入的文本

*First, the user’s recent input is copied into the “#user_question” DIV.  Next, an AJAX request is crafted with caching set to FALSE so we always get a fresh response from the chatbot, and an anonymous completion handler is defined that does the following (attached to the JQuery AJAX done() event): *

首先,将用户的最新输入复制到``#user_question'‘DIV中.接下来,将缓存设置为FALSE来制作AJAX请求,因此我们总是会从聊天机器人获得新的响应,并定义一个匿名完成处理程序来执行以下操作(附加到JQuery AJAX done()事件上):

• Clears the “#entry” textarea to make way for new input from the user清除" #entry"文本区域,以便为来自用户的新输入让路
• *Extracts the response message using regular expressions from the  element ChatRelay.cshtml embeds in the rendered web page.*使用正则表达式从呈现的网页中的 元素ChatRelay.cshtml嵌入中提取响应消息.

This pattern repeats until the user is finished chatting with the chatbot.  At this point we have created a complete chatbot system with ChatScript at its core running on an Ubuntu Linux VM, a proxy or relay page to make the chatbot available via AJAX friendly HTTP requests, and a web page with a friendly interface for the user to interact with that facilitates the chat session.  Now it’s time to work on the chatbot itself.

重复此模式,直到用户完成与聊天机器人的聊天为止.至此,我们已经创建了一个完整的聊天机器人系统,其以运行在Ubuntu Linux VM上为核心的ChatScript,一个代理或中继页面(可通过AJAX友好的HTTP请求使该聊天机器人可用)以及一个具有友好界面的网页供用户使用与之互动可以促进聊天会话.现在是时候在chatbot本身上工作了.

A Simple Chatbot for Lost & Found Visitors (失物招领者的简单聊天机器人)

*Here are is a sample interaction between a user and the simple chatbot I implemented for the Lost & Found web site.  Note, I am displaying the discourse as a linear series of interactions instead of a bulky stream of screenshots using the actual GUI interface shown in Step 10, which only shows the latest user input and chatbot response.  Also, the chatbot’s internal name is Harry and I have arbitrarily given the visiting user the name CatLover17.  As mentioned before, the user’s IP address is currently being used as a guest ID : *

这是用户与我为"失物招领"网站实现的简单聊天机器人之间的示例交互.请注意,我使用第10步中显示的实际GUI界面,以线性交互的形式显示了论述,而不是大量的屏幕截图,该界面只显示了最新的用户输入和聊天机器人的响应.此外,聊天机器人的内部名称是Harry,我已经为访问用户任意指定了名称CatLover17.如前所述,该用户的IP地址当前用作来宾ID:

HARRY:_ Hello, welcome to FindAPet. How can I help you?
CatLover17:_> How much does it cost to use the Lost & Found?
HARRY:_ There is no charge to use the Lost & Found system.
CatLover17:_> Do I need to have a credit card?
HARRY:_ No you do not. There is no charge to use the Lost & Found system.
CatLover17:_>

*Here are the ChatScript rules that facilitated this exchange: *

以下是促进交换的ChatScript规则:

# These rules handle questions from the user regarding
#  the cost of using the system.
#
#!x*** COST OF THE SYSTEM

#! How much does it cost to use the system?
u: FREE (how much)
	There is no charge to use the Lost & Found system.
	
#! Is it free?
u: (is * free)
	^reuse(FREE)	

#! What is the cost to use the system?
u: (what * cost)
	^reuse(FREE)	
	
#! Do I need a credit card?
u: (credit card)
	No you do not.
	^reuse(FREE)	

*Comment lines in ChatScript begin with the hash “#” character.  However, lines that start with a hash character followed by an exclamation point ("#!") have a very special meaning.  They are rule test comments and the “#!” is the rule test prefix.  You can use the “:verify” meta-command to ask ChatScript to verify the rules in your topic file.  ChatScript will take the example sentence that follows the rule test prefix and apply it to the rule immediately following it, as if the user entered it during a session.  If the rule fails to match against the example sentence, a warning will be printed out.  This is very useful for unit testing your chatbot when you make a lot of new changes that might have broken older rules in the system!  *

ChatScript中的注释行以井号"#“开头.但是,以井号字符开头并带有感叹号("#!")的行具有非常特殊的含义.它们是规则测试注释和”#!“是规则测试前缀.您可以使用”:verify"元命令要求ChatScript验证主题文件中的规则. ChatScript将使用规则测试前缀后面的示例句子,并将其应用于紧随其后的规则,就像用户在会话期间输入它一样.如果规则与例句不匹配,将打印警告.当您进行许多可能会破坏系统中旧规则的新更改时,这对于单元测试聊天机器人非常有用!

Rule Structure (规则结构)

ChatScript rules have the following structure:

ChatScript规则具有以下结构:

*[rule type]: {rule label} (match pattern) body *

[身体]

*[rule type]: The rule type is a single character from a set consisting of the 4 different rule types, and it is required: *

• "?" - the rule will only match (or “fire”) if the user asked a question and the content of the question is matched by the match pattern."？" -仅当用户提出问题且匹配模式匹配问题内容时,规则才会匹配(或"触发").
• “s” - the rule will only match if the user made a non-interrogatory response and the content of the statement is matched by the match pattern." s"-该规则仅在用户做出非疑问响应且该语句的内容由匹配模式进行匹配时才匹配.
• “u”- the union of “?” and “s”.  The rule will match if the match pattern matches the content of the last user input, regardless of the input type, so questions or a statements are considered for a match." u"-"？“的并集和” s".如果匹配模式匹配最后一次用户输入的内容,则该规则将匹配,而不管输入类型如何,因此将考虑问题或陈述以进行匹配.
• “t” - The topic gambit.  This is a statement the chatbot will display to the user if the chatbot has control of the conversation, which happens when it is not currently reacting to a question or statement made by the user." t"-主题倾向.如果聊天机器人可以控制对话,则这是聊天机器人将向用户显示的一条语句,这是在聊天机器人当前未对用户提出的问题或陈述做出反应时发生的.

*{rule label}: A rule label is a constant that exists solely to allow other rules to refer to it.  It is optional, and you will see an example of one shortly.  Rule labels are optional.  *

{rule label}:规则标签是一个常数,仅存在以允许其他规则引用它.它是可选的,不久您将看到一个示例.规则标签是可选的.

*(match pattern): The match pattern is the expression that ChatScript will apply against the user’s input to decide whether or not to execute the rule. *

(匹配模式):匹配模式是ChatScript将对用户输入应用的表达式,以决定是否执行规则.

*body: The body of the rule that contains the actions to take if the rule fires.  These actions can include: setting internal variables, chaining to other rules, displaying text to the user, and more. *

Pattern Matching  (模式匹配)

IMPORTANT:  One of the powerful features built-in to ChatScript is its ability to canonicalize words in the user’s input.  This allows you to write concise rules that can handle many different sentence patterns with a minimum of effort because ChatScript is helping you to generalize your match  pattern.  For example, the canonical form of a verb is the infinitive tense.   If you used the word “be” in a match pattern it would match “[is, was, are, etc.]” since they are all forms of the verb “be”.

重要说明:ChatScript内置的强大功能之一是它能够规范化用户输入中的单词.这使您可以编写简洁的规则,以最少的努力即可处理许多不同的句子模式,因为ChatScript可以帮助您概括匹配模式.例如,动词的规范形式为不定式时态.如果在匹配模式中使用单词" be",它将匹配" [is,was,are,etc.]",因为它们都是动词" be"的形式.

*Let’s take one of the rules from the rules above that respond to user input concerning the cost of the Lost & Found system: *

让我们从上面的规则中选择一个规则,这些规则可以响应用户有关"失物招领"系统成本的输入:

u: FREE (how much)
	There is no charge to use the Lost & Found system. 

The rule type is “u” indicating the rule will respond to any input from the user.  The match pattern is simply the words “how” and “much”.  This rule will fire if the user’s input contains the words “how much” anywhere in the sentence, as long as they appear in the same order as the match pattern.  Therefore the following sentences and many others will trigger this rule:

规则类型为" u",表示规则将响应用户的任何输入.匹配模式只是单词" how"和" much".如果用户的输入在句子中的任何位置包含单词"多少",只要它们以与匹配模式相同的顺序出现,该规则就会触发.因此,以下句子和许多其他句子将触发此规则:

• *How much does the system cost?*系统费用是多少？
• *How much does it cost to use the system?*使用该系统需要多少费用？
• (Any other sentence that has “how much” in it in the same word order).(在同一词序中具有"多少"的任何其他句子).

If this rule triggers than the sentence “There is no charge to use the Lost & Found system” will be displayed to the user since that is the only action found in the rule’s body.

如果触发此规则,则将向用户显示句子"免费使用"失物招领发现系统",因为这是在规则正文中找到的唯一操作.

Rule Labels and the Reuse Keyword(规则标签和重用关键字)

Here’s the second rule that responds to input from the user regarding the cost of the system:

这是第二条规则,它响应用户有关系统成本的输入:

u: (is * free)
	^reuse(FREE)

ChatScript match pattern’s can contain wildcard characters that are used in a manner similar to that found in regular expressions.  It will consume 0 or more words in a sentence during the matching process.   In the match pattern (is * free), this means that pattern will match any sentence that has “is” in it and “free” in it, even if there are 1 or more words in-between them.  Therefore, this rule will match the following sentences:

ChatScript匹配模式可以包含通配符,其使用方式类似于正则表达式中的通配符.在匹配过程中,它将消耗一个句子中的0个或多个单词.在匹配模式中(is * free),这意味着该模式将匹配其中有is''和其中有free'‘的任何句子,即使它们之间有1个或多个单词也是如此.因此,此规则将匹配以下句子:

• *Is it free?*免费吗？
• *Is the system free?*系统免费吗？
• *Is the system always free for users?*该系统始终对用户免费吗？
• (any sentence with “is” in it followed by “free”, with 0 or more words between them)(任何带有" is"的句子,后跟" free",并且其中包含0个或多个单词)

*Wildcards widen the number of sentences a match pattern can match, increasing its flexibility, but at the potential cost of matching unwanted sentences too and increasing the likelihood that the rule will interfere with other rules in the topic.  The tip above about specific vs. general rules applies here too. *

通配符扩大了匹配模式可以匹配的句子数量,增加了灵活性,但同时也可能会匹配不需要的句子,并增加了规则干扰主题中其他规则的可能性.上面有关特定规则与一般规则的提示也适用于此.

*Take a quick look again at the rules list above for the rules that handle user questions about the cost of the system.  Notice that all the rules following the first rule have the same body that contains the single action to reuse the rule labeled FREE.  The reuse keyword eliminates the need to duplicate rule bodies between rules that perform the same basic task in response to user input that means roughly the same thing.  The task in this context is to display the message “There is no charge to use the Lost & Found system” to the user when they ask about the system’s cost.  Without the reuse keyword we would have to duplicate that action across all the rules.  However, each rule is free to take its own actions as well as you can see in the credit card rule: *

再次快速浏览一下上面的规则列表,以了解处理用户关于系统成本的问题的规则.请注意,第一个规则之后的所有规则具有相同的主体,该主体包含用于重用标记为FREE的规则的单个操作.重用关键字消除了需要在执行相同基本任务的规则之间重复规则主体以响应用户输入的含义,即用户表示大致相同的内容.在这种情况下,任务是在用户询问系统成本时向用户显示消息"使用Lost＆Found系统不收费".没有重用关键字,我们将不得不在所有规则中重复执行该操作.但是,每条规则都可以自行采取行动,就像您在信用卡规则中所看到的那样:

u: (credit card)
	No you do not.
	^reuse(FREE)

That rule first displays the message “No you do not.” to the user before passing control to the first rule.  The net output to the user then becomes: “No you do not.  There is no charge to use the Lost & Found system”.  This gives you tremendous flexibility in crafting succinct rules that can handle many different situations, with a minimum of unnecessary duplication between the contents of each rule.

该规则首先显示消息"不,您不这样做".在将控制权传递给第一条规则之前向用户显示.然后向用户输出的净值将变为:``不,您不可以.使用Lost＆Found系统不收费’'.这为您提供了精巧的精巧规则,可以处理许多不同的情况,并且每个规则的内容之间没有不必要的重复.

Rejoinders.  Rules with Context. (重新加入.具有上下文的规则.)

*Frequently you have questions or responses that are only relevant in the context of a previous question or response.  ChatScript has rules that are in a class known as rejoinders.  Take a look at the rules below.  Note that the rules below belong to the ~questions topic, as indicated by the first line, not the ~introductions topic.  The repeat, keep, and nostay keywords will be discussed in a minute:  *

通常,您遇到的问题或答案仅与先前的问题或答案相关. ChatScript具有规则,该规则在称为重新联接器的类中.看看下面的规则.请注意,如第一行所示,以下规则属于〜questions主题,而不是〜introductions主题.稍后将讨论重复,保留和Nostay关键字:

topic: ~questions repeat keep nostay []

# Do we know if the user has a photo?
u: (!$hascatphoto)
	Do you have a photo of your cat?
	
	# Rejoinder looking for "yes" response or equivalent.
	a: (~yes)
		Good. When we are done talking, please upload it to the Lost & Found.
	
		# Remember that they have a photo.
		$hascatphoto = true
		
		# Ask the next relevant question.
		^respond(~questions)
		
	# Rejoinder looking for "no" response or equivalent.
	a: (~no)
		OK.  
		
		# Remember that they don't have a photo.
		$hascatphoto = false
		
		# Ask the next relevant question.
		^respond(~questions)

Variables and Word Sets (变量和单词集)

This gives me a chance to talk about variables and word sets now.  Variable names in ChatScript are prefixed with a dollar sign ("$b").  ChatScript also supports the negation operator symbolized by the exclamation point “!”.  Therefore, the match pattern of the top level rule here matches if the $hascatphoto variable is undefined, indicating we have not gotten an answer yet from the user as to whether or not they have a photo of their lost cat.  If this rule fires, it immediately displays the message “Do you have a photo of your cat?” and waits for the user to respond.

这使我有机会现在谈论变量和单词集. ChatScript中的变量名称以美元符号(" $ b")为前缀. ChatScript还支持由感叹号"!“表示的取反运算符.因此,如果$ hascatphoto变量未定义,则此处顶级规则的匹配模式将匹配,这表明我们尚未从用户那里获得关于是否有丢失猫的照片的答案.如果触发此规则,它将立即显示消息"您有猫的照片吗？“并等待用户响应.

This is where rejoinders come into play.  All rejoinder rules must start with a single letter in the range of “a through q”, taking the place of one of the 4 rule types discussed earlier.  This letter indicates the rejoinder nesting depth.  Rejoinders can be nested and if so, the letter should advance to the next letter in the alphabet at each depth (i.e. - “a:”, “b:”, “c:”, etc.).  Since our example only goes one level down, both rejoinders have “a:” for the rejoinder nesting depth character.  The example shows two rejoinder rules, one for handling a yes response from the user and the other one for handling a no response.

这是重新加入比赛的地方.所有重新连接规则都必须以一个从” a到q"范围内的单个字母开头,以代替前面讨论的4种规则类型之一.该字母表示再接合器的嵌套深度.可以嵌套重连词,如果这样,则字母应在每个深度处前进到字母表中的下一个字母(即-” a:"," b:"," c:“等).由于我们的示例仅下降了一层,因此两个重新连接器的重新连接器嵌套深度字符都具有``a:''.该示例显示了两个重新联接规则,一个用于处理用户的是响应,另一个用于处理不响应.

*Notice that the words no and yes are preceded by a tilde ("~") character.  In the case of (~yes) This tells ChatScript to match any response that equates to a positive response (yes, sure, OK, etc.)  In the case of (~no) This tells ChatScript to match any response that equates to a negative response (no, nope, etc.).  When a word is preceded by a tilde character it indicates the word is actually the name of a concept set.  Concept sets are lists of words that represent the same semantic meaning, at least as far as a rule is concerned, and can be reused throughout your chatbot to eliminate the duplication of common word lists when crafting topic rules. *

请注意,在单词no和yes之前加上波浪号(〜).在(〜是)的情况下,它告诉ChatScript匹配等于肯定响应的任何响应(是,肯定,确定等).在(〜否)的情况下,它告诉ChatScript匹配任何等于肯定响应的响应.负面反应(不,不,等等).当单词前面有波浪号字符时,表示该单词实际上是概念集的名称.概念集是至少在规则方面表示相同语义含义的单词列表,并且可以在整个聊天机器人中重用,从而在编写主题规则时消除了常见单词列表的重复.

Notice that the different value each rejoinder assigns to the $hasphoto variable.  You will see later how this affects the chatbot’s interaction with the user.

请注意,每个重新连接器分配给$ hasphoto变量的不同值.稍后您将看到这如何影响聊天机器人与用户的交互.

The Respond keyword (响应关键字)

*You can also see that each rejoinder ends with a respond statement.  Since the word ^respond is preceded by a tilde, this indicates it’s a ChatScript function call.  The statement ^respond(~questions) tells ChatScript to make a call to the ~questions topic.   However, as mentioned previously, the rejoinder rules shown here are members of the ~questions topic so this works out to a recursive call into the topic.  This is done to make sure that every question that needs to be answered by the user gets a chance to execute.  To solidify our knowledge here is a brief description of another rule in the ~questions topic.  Take a look at the rule that asks the user for the cat’s breed: *

您还可以看到每个重新连接器都以一个response语句结尾.由于单词^ respond前面带有波浪号,因此表示它是一个ChatScript函数调用.语句^ respond(〜questions)告诉ChatScript调用〜questions主题.但是,如前所述,此处显示的重新连接规则是〜questions主题的成员,因此可以对该主题进行递归调用.这样做是为了确保用户需要回答的每个问题都有执行的机会.为了巩固我们的知识,这里是〜questions主题中另一个规则的简短描述.看一下询问用户猫的品种的规则:

#!x*** CAT BREED

# TIP: This rule must follow the other cat breed rules becaue it is more general than
#  they are and will fire before they do.		
#
u: (!$hasbreed)
	What breed is your missing cat?  If more than one, just list them.		

	# My cat's breed is.
	a: ASKCATBREED (is _*)
		$catbreed = '_0
	
	# Just accept the user's last input as the entire answer to the breed question.	
	a: (_*)
		^reuse(ASKCATBREED)

The rule’s match pattern indicates it will fire if we don’t have a valid value for the variable $hasbreed yet.  This rule introduces you to the subject of capture variables, another concept familiar to those who work with regular expressions.  If you look at the match patterns for the rejoinders used by this rule, you’ll see the word “is” followed by an underscore prefixing a wildcard ("_").  This tells ChatScript to capture all of the user’s input that follows the word “is”.   For example, if the user said “My cat is a tabby cat” ChatScript would assign the words “is a tabby cat” to the $catbreed variable.  Capture variables are accessed in the body of a rule by using capture variable index labels.  These index labels are numbered from 0 upwards and correspond positionally to the order in which content was captured from the user’s input.  Since we only have one capture group, to access the content of that group and assign its value to the $catbreed variable we use “_0” as the capture variable index label.  In this case the value of the capture group is the text “is a tabby cat”.  The reason for prefixing the capture variable index label with an apostrophe ("'") is to keep ChatScript from trying to interpret or modify the value of the capture group before handing it over to the $catbreed variable.  You will find lots of interesting information about ChatScript’s built-in text processing features in the Basic and Advanced user manuals.  However, in this case we want exactly what the user typed without modification, since it’s a cat breed and not a common word or phrase.*

规则的匹配模式表示如果变量$ hasbreed还没有有效值,它将触发.此规则为您介绍捕获变量的主题,这是使用正则表达式的人员所熟悉的另一个概念.如果您查看此规则使用的重连词的匹配模式,则会看到单词is'',后跟带下划线的通配符(_ *'').这告诉ChatScript捕获单词” is"之后的所有用户输入.例如,如果用户说"我的猫是虎斑猫",ChatScript会将单词"是虎斑猫"分配给$ catbreed变量.通过使用捕获变量索引标签可以在规则主体中访问捕获变量.这些索引标签从0向上编号,并且位置对应于从用户输入中捕获内容的顺序.因为我们只有一个捕获组,所以要访问该组的内容并将其值分配给$ catbreed变量,我们使用" _0"作为捕获变量索引标签.在这种情况下,捕获组的值为文本"是虎斑猫".为捕获变量索引标签加上撇号("'")的原因是,防止ChatScript在将捕获组的值移交给$ catbreed变量之前尝试解释或修改捕获组的值.在"基本"和"高级"用户手册中,您会找到许多有关ChatScript内置文本处理功能的有趣信息.但是,在这种情况下,我们希望用户输入的内容无需修改即可,因为它是猫的品种,而不是常见的单词或短语.

Putting It All Together (放在一起)

*I am reproducing the rules for the entire questions gauntlet  below so I can describe the overall pattern of interaction to you, to make sure you get the global picture of what is happening here: *

我将在下面重现所有问题的规则,以便我可以向您描述互动的总体模式,以确保您了解此处正在发生的事情的全局情况:

#!x*** QUESTIONS GAUNTLET

# This topic keeps asking questions until the user provides the basic
#  information needed to help find their cat.

topic: ~questions repeat keep nostay []

#!x*** USER PHOTO OF CAT

# Do we know if the user has a photo?
u: (!$hascatphoto)
	Do you have a photo of your cat?
	
	# Rejoinder looking for "yes" response or equivalent.
	a: (~yes)
		Good. When we are done talking, please upload it to the Lost & Found.
	
		# Remember that they have a photo.
		$hascatphoto = true
		
		# Ask the next relevant question.
		^respond(~questions)
		
	# Rejoinder looking for "no" response or equivalent.
	a: (~no)
		OK.  
		
		# Remember that they don't have a photo.
		$hascatphoto = false
		
		# Ask the next relevant question.
		^respond(~questions)
		
#!x*** CAT'S NAME

# TIP: This rule must follow the other cat name rules becaue it is more general than
#  they are and will fire before they do.		
#
# Do we know the cat's name?
u: (!$catname)
	# Set a variable so we know the last question we asked was the cat's name.
	$askcatname = true
	What is the name of your cat?
	
	#! My cat's name is Malfie
	a: ASKCATNAME (is _*)
		# Save the cat's name. We prepend an apostrophe so that
		#  ChatScript does not attempt to interpret the cat's name
		#  and will give it to us unaltered as given by the user.
		$catname = '_0
		
		# Ask the next relevant question.
		^respond(~questions)
		
	#! I call her Trixie.
	a: (call* * _*)
		^reuse(ASKCATNAME)
		
	# This pattern is the catch-all in case the above patterns don't match since
	#  the user just said the cat's name as a response.
	#! Trixie.	
	a: (_*)
		^reuse(ASKCATNAME)

#!x*** CAT BREED

# TIP: This rule must follow the other cat breed rules becaue it is more general than
#  they are and will fire before they do.		
#
u: (!$hasbreed)
	What breed is your missing cat?  If more than one, just list them.		

	# My cat's breed is.
	a: ASKCATBREED (is _*)
		$catbreed = '_0
	
	# Just accept the user's last input as the entire answer to the breed question.	
	a: (_*)
		^reuse(ASKCATBREED)

* As you can see, the questions gauntlet consists of three rules that each get one piece of information from the user about their lost cat.  In order they are: Photo Yes/No, Name, and Breed.  With each acquisition, the input received is assigned to the correct variable.  In order they are: $hasphoto, $catname, and $catbreed.*

如您所见,问题手套由三个规则组成,每个规则都从用户那里获得有关其迷路猫的一条信息.它们的顺序为:照片是/否,名称和品种.每次采集时,接收到的输入都会分配给正确的变量.它们的顺序为:$ hasphoto,$ catname和$ catbreed.

But how do the parts all fit together?  Once the question gauntlet has control, it keeps calling itself recursively using the ^respond(~questions) statement covered earlier, that each rule except the last rule finishes with.  The reason that the last rule doesn’t have a call to ^respond is because by the time it is executed and gets the answer it is looking for, all the questions have been answered and the ~questions topic is finished.  If we added more questions after the CAT BREED rule in the topic, we would have to add a trailing ^respond call to it too.

但是各部分如何装配在一起？一旦问题控制权得到控制,它将继续使用前面介绍的^ respond(〜questions)语句递归地调用自身,最后一条规则除外的每个规则都将以其结束.最后一条规则没有调用^ respond的原因是因为在执行该规则并获得要查找的答案时,所有问题都已得到回答,〜questions主题已完成.如果我们在该主题的CAT BREED规则之后添加了更多问题,我们也必须为其添加尾随^ respond调用.

The last piece of the puzzle is to display to the user the knowledge we have accumulated about their cat.  Take a look at these two rules that belong to the ~introductions topic, not the ~questions topic:

难题的最后一部分是向用户显示我们积累的有关猫的知识.看一下属于引言主题而不是问题题的这两个规则:

# If we have successfully collected the basic information
#  we need from the user, summarize it and display it back
#  to the user with the proper adjustment made for whether
#  or not the user has a photo of their lost cat.  Otherwise,
#  we keep asking questions until we do.
#
#!x*** SUMMARIZE USER INFORMATION AND DISPLAY

# User has provided all the required information and has a photo.				
u: ($catname $catbreed $hascatphoto=true)
	Ok.  You said your cat's name is $catname
	and that the breed was $catbreed and that
	you have a photo.  You are now ready to
	use the Lost & Found system. 

# User has provided all the required information and does not have
#  has photo.				
u: ($catname $catbreed $hascatphoto=false)
	Ok.  You said your cat's name is $catname
	and that the breed was $catbreed and that
	you do not have a photo.  You are now ready to
	use the Lost & Found system.  However, if you
	find a photo of your lost cat, please return here
	and upload it to the system.

# User has not provided all the required information yet.
#  
u: (!$catname)
	^respond(questions)
u: (!$catbreed)
	^respond(questions)
u: (!$hasphoto)
	^respond(questions)

Look at the first rule that has the match pattern of ($catname $catbreed $hascatphoto=true).  This rule will fire when $catname and $catbreed have valid values, and $hascatphoto has the value of true.  In other words, this rule will fire when all 3 pieces of information have been acquired from the user and the user indicated that they have a photo of their lost cat.  It will read back the values the user gave and tell them they are ready to use the Lost & Found system.

查看具有匹配模式($ catname $ catbreed $ hascatphoto =true)的第一条规则.当$ catname和$ catbreed具有有效值且$ hascatphoto具有true值时,将触发此规则.换句话说,当从用户处获取了所有3条信息并且用户指示他们有丢失的猫的照片时,此规则将触发.它将读回用户提供的值,并告诉他们他们准备使用"失物招领"系统.

The second rule is almost identical except it will fire instead of the first rule if the user indicated that they did not have a photo of their lost cat.  In that case, the values acquired will again be read back to the user with the suggestion that they return and upload a photo of their cat, if they later find one.

第二条规则几乎相同,只是如果用户指示他们没有丢失的猫的照片,它将代替第一条规则触发.在这种情况下,如果以后找到了它们,将再次将获取的值读回用户,并建议他们返回并上传猫的照片.

The last three rules shown in the last above are there to trigger the question gauntlet if any of the required variables still do not have a valid value yet.  Each one checks to see if a specific variable does not have a valid value yet and if so, control is transferred to the questions gauntlet.

如果任何必需变量仍没有有效值,则上面最后一部分中显示的后三个规则可以触发问题手套.每个人都检查以查看特定变量是否尚无有效值,如果有,则将控制权转移到问题手套.

That is how the different parts of the rules in our topic file interact and how control is transferred between topics.  On that note here’s a brief discussion of the keep, repeat, and nostay topic keywords.

这就是主题文件中规则的不同部分之间如何交互以及主题之间如何转移控制的方式.关于这一点,这里是keep,repeat和nostay主题关键字的简短讨论.

Avoiding Repetition and Topic Flow Control (避免重复和主题流控制)

The chatbot demonstrated here that provides help to Lost & Found visitors is a simple chatbot.  We are not trying to tell a story, but merely trying to answer a few common questions the user may have and obtain 3 pieces of information necessary to search nearby humane shelters for the user’s cat.  Therefore, within reason, we don’t care if we repeat ourselves and we are not looking to create the illusion of being a real character in a story.  More elaborate storytelling chatbots work very hard to avoid repetition, something that did not concern us.  ChatScript has several features to enforce variety in the output from a chatbot.  These features are covered in detail in the ChatScript documentation.  However, in the interest of being thorough here is a terse discussion of the the repetition and topic flow control keywords you saw in this article:

这里演示的聊天机器人可以为失物招领处的访问者提供帮助,它是一个简单的聊天机器人.我们不是在讲故事,而只是在回答用户可能遇到的一些常见问题,并获得3条信息,以搜索附近的人类庇护所来寻找用户的猫.因此,在合理的范围内,我们不在乎是否重复自己,也不想在故事中制造真实角色的幻想.为了避免重复,更复杂的讲故事聊天机器人会非常努力地工作,这与我们无关. ChatScript具有多种功能,可增强聊天机器人输出的多样性.这些功能在ChatScript文档中详细介绍.但是,为了使您更全面,这里对您在本文中看到的重复和主题流控制关键字进行了简短的讨论:

• *repeat - Normally a rule is not allowed to produce duplicate output to the user.  That is, it is not allowed to repeat itself.  Adding this keyword allows a rule to repeat itself, making it easier to craft a lightweight chatbot.*重复-通常不允许规则向用户产生重复的输出.也就是说,不允许重复自己.添加此关键字允许规则重复其自身,从而使制作轻量级聊天机器人更加容易.
• *keep - The default setting for the ChatScript engine is to “discard” a rule after it has been used.  This makes sure that all or most rules in the chatbot get a chance to execute, creating additional variety.  The keep keyword defeats this mechanism and allows a rule to be reused endlessly.*keep-ChatScript引擎的默认设置是在使用规则后"丢弃"该规则.这确保了聊天机器人中的所有或大多数规则都有执行的机会,从而创造了更多种类. keep关键字破坏了这种机制,并允许无休止地重用规则.
• *nostay - Normally ChatScript will stay inside of a topic until it is exhausted.  In our chatbot’s case we want it to exit the ~questions topic as soon as a piece of information was obtained from the user.  The reason we still get all 3 pieces of information once we enter the topic is due to the recursive call we make to the ~questions topic with the help of the ^respond(~questions) statement.  Once all 3 recursive calls exit back to the top, control is immediately transferred back to the ~introductions topic.  If it weren’t for the nostay keyword, we would stay in the ~questions topic instead, an unwanted behavior.*nostay-通常,ChatScript将保留在主题内,直到用尽为止.对于我们的聊天机器人,我们希望它在从用户那里获得一条信息后立即退出〜questions主题.进入主题后我们仍会获得所有3条信息的原因是由于我们借助^ respond(〜questions)语句对〜questions主题进行了递归调用.一旦所有3个递归调用都返回顶部,控件将立即转移回〜introductions主题.如果不是不必要的关键字,那么我们将停留在〜questions主题中,这是不想要的行为.

The Net Result - A Full Chat Session Log (最终结果-完整的聊天会话日志)

Here is an actual chat log that shows a full session with a user.  As you read it, see if you can map your new knowledge on how the rules work to what is happening between the user and the chatbot:

这是一个实际的聊天记录,显示与用户的完整会话.阅读时,请查看是否可以将有关规则如何工作的新知识映射到用户与聊天机器人之间发生的情况:

HARRY:_ Hello, welcome to FindAPet. How can I help you?
CatLover17:_> How much does it cost to use the Lost & Found?
HARRY:_ There is no charge to use the Lost & Found system.
CatLover17:_> Do I need a credit card?
HARRY:_ No you do not. There is no charge to use the Lost & Found system.
CatLover17:_> What do I do to use it?
HARRY:_ Do you have a photo of your cat?
CatLover17:_> Yes I do.
HARRY:_ Good. When we are done talking, please upload it to the Lost & Found. 
What is the name of your cat?
CatLover17:_> Her name is Roxy.
HARRY:_ What breed is your missing cat? If more than one, just list them.
CatLover17:_> Roxy is an Oriental Short-Hair.
HARRY:_ Ok. You said your cat's name is Roxy and that the breed was 
an Oriental Short hair and that you have a photo. 
You are now ready to use the Lost & Found system.
CatLover17:_>

*  A Final Note About ChatScript   *

关于ChatScript的最后说明

*A chatbot is only as sophisticated and clever as you make it.    Fortunately with ChatScript you can make it as sophisticated and clever as you want due to its extensive capabilities of which only a tiny fraction was covered in this article.  Yet even this simple chatbot adds real value to the Lost & Found web site, saving the user from wading through help pages or FAQs while answering key questions they have about how the site works.  *

聊天机器人只有像您创建的那样复杂和聪明.幸运的是,由于ChatScript具有强大的功能,因此您可以使它变得既复杂又聪明,因为本文仅涉及其中的一小部分.但是,即使这个简单的聊天机器人也为"失物招领"网站增添了真正的价值,使用户免于浏览帮助页面或常见问题解答,同时回答了他们对网站运作方式的关键问题.

Azure make provisioning and configuring a virtual machine easy and a virtual machine is the gateway to adding high power value to your site by providing killer web services that go above and beyond the capabilities of a common web site or web service.  Azure is equally adept at supporting non-Windows operating systems so if your favorite tool only runs under, or runs best under Linux or some other exotic operating environment there is nothing stopping you from implementing it.  Finally, a wonderful concrete example of a scenario that requires a virtual machine is a chatbot.  With ChatScript you can add an entertaining and informative virtual assistant easily to your web site, hosted by Azure, and powered by a Linux virtual machine.  You can talk to the Lost & Found ChatBot using the link below:

Azure使配置和配置虚拟机变得容易,虚拟机是通过提供超越普通网站或Web服务功能的杀手级Web服务,为您的站点增加高功率价值的网关. Azure同样擅长于支持非Windows操作系统,因此,如果您最喜欢的工具仅在Linux或其他奇特的操作系统下运行,或在Linux或其他奇特的操作系统下运行效果最佳,则没有什么会阻止您实施它.最后,一个需要虚拟机的场景的精彩示例是聊天机器人.使用ChatScript,您可以轻松地将娱乐性和信息量丰富的虚拟助手添加到您的网站,由Azure托管并由Linux虚拟机提供支持.您可以使用以下链接与"失物招领"聊天室进行交谈:

 Talk to the Lost & Found ChatBot (与失物招领聊天室交谈)

许可

本文以及所有相关的源代码和文件均已获得The Code Project Open License (CPOL)的许可。