The Snap Framework: a Web Toolkit for Haskell

Total Page:16

File Type:pdf, Size:1020Kb

The Snap Framework: a Web Toolkit for Haskell The Functional Web The Snap Framework A Web Toolkit for Haskell Gregory Collins • Google Switzerland Doug Beardsley • Karamaan Group askell is an advanced functional pro- the same inputs, always produce the same out- gramming language. The product of more put. This property means that you almost always H than 20 years of research, it enables rapid decompose a Haskell program into smaller con- development of robust, concise, and fast soft- stituent parts that you can test independently. ware. Haskell supports integration with other Haskell’s ecosystem also includes many power- languages and has loads of built-in concurrency, ful testing and code-coverage tools. parallelism primitives, and rich libraries. With Haskell also comes out of the box with a set its state-of-the-art testing tools and an active of easy-to-use primitives for parallel and con- community, Haskell makes it easier to produce current programming and for performance pro- flexible, maintainable, high-quality software. filing and tuning. Applications built with GHC The most popular Haskell implementation is enjoy solid multicore performance and can han- the Glasgow Haskell Compiler (GHC), a high- dle hundreds of thousands of concurrent net- performance optimizing native-code compiler. work connections. We’ve been delighted to find Here, we look at Snap, a Web-development that Haskell really shines for Web programming. framework for Haskell. Snap combines many other Web-development environments’ best fea- What’s Snap? tures: writing Web code in an expressive high- Snap offers programmers a simple, expressive level language, a rapid development cycle, fast Web programming interface at roughly the same performance for native code, and easy deploy- level of abstraction as Java servlets. It includes a ment in production. fast, built-in HTTP server that drives application logic, so you can quickly create high-performance Why Is Haskell Good Web applications. Unlike some other Web frame- for Web Programming? works in higher-level languages, Snap lets you Haskell lets you write elegant, high-level code consume request data and stream response data that rivals the performance of lower-level, using a constant amount of memory. imperative languages. You can write declara- Snap features excellent documentation and tive programs at a high level of abstraction and tutorial materials, and, for a young project, it’s expressiveness, while still maintaining excel- quite robust. Haskell’s testing tools let you eas- lent performance. When you need to do bare- ily write a test suite with a high level of cover- metal bit-twiddling or need access to a C library age. Snap uses Haskell’s cross-platform libraries that doesn’t yet have a Haskell equivalent, its to run on all major operating systems. A Snap- foreign function interface lets you easily drop based application also supports rapid develop- down to C. ment — an app running in development mode Writing solid, real-world code is easier in will load changes to your source code as soon Haskell than in other languages. It has strong as you make them. When you put your code into static typing, so many common programming production, you can create a single, fast, stand- errors, such as null pointer exceptions, can’t alone executable that’s easy to deploy. occur. You can separate an application’s core We designed Snap for efficiency; where logic from the parts that must interact with the appropriate, we use fast system calls such as outside world: “pure” functions in Haskell, given sendfile() and epoll(). On older versions of 84 Published by the IEEE Computer Society 1089-7801/11/$26.00 © 2011 IEEE IEEE INTERNET COMPUTING The Snap Framework data ApplicationState = ApplicationState GHC, we have an optional binding { templateState :: HeistState Application to the libev C library for high-scal- , timerState :: TimerState ability I/O event scheduling. } Getting Started with Snap Figure 1. The ApplicationState data type contains in-memory application Snap requires the Haskell platform state, which persists between requests. (http://hackage.haskell.org/platform), which ships with a binary installer for most major platforms. The Haskell platform includes the GHC applicationInitializer :: Initializer ApplicationState compiler, documentation, libraries, applicationInitializer = do and tools; think of it as “Haskell: heist <- heistInitializer “resources/templates” batteries included.” emptyTemplateState Once you’ve installed the Haskell timer <- timerInitializer platform, you can download, build, return $ ApplicationState heist timer and install Snap’s framework and all its dependencies using the cabal Figure 2. An Initializer handles a Snap application’s startup, reloads, and package manager: cleanup. $ cabal update $ cabal install snap $ cabal install the ApplicationState type, which $ myproject -p 8000 we’ll define next (see Figure 1). The Snap installation builds the Snap applications hold some state snap executable, which you can use Now, point your Web browser to in memory that they use to service to get started with a basic Snap proj- http://localhost:8000/; the server requests. Things in this category ect. By default, cabal installs exe- should respond with the default include templates and caches. In our cutables to $HOME/.cabal/bin; the canned response. particular case, ApplicationState following instructions assume that contains the set of templates we use this directory is on your $PATH. Programming with Snap: to service user requests (using our To set up a new example Snap A Simple Example heist templating library), as well as project (which is intended for use as Let’s look more closely at what’s in a TimerState, an example extension an example or jumping-off point for the default skeleton application. that stores the last time the applica- your own Snap Web applications), (This article describes a prerelease tion was reloaded. run these commands: version of Snap 0.3, which is sched- Application.hs also includes uled to be released before this issue code to initialize the application on $ mkdir myproject goes to print. Some details might load or reload. In Snap, we call this $ cd myproject change slightly.) code an Initializer, which handles $ snap init The snap init command creates a a Snap application’s startups, reloads, few files in thesrc/ subdirectory, the and cleanup (see Figure 2). This code The snap init command creates important ones being Application. loads all the template files from the a skeletal Snap project in the current hs, which contains the application’s resources/templates directory, ini- directory. This is a complete work- state definitions, and Site.hs, which tializes the reload timer, and creates ing Snap application that doesn’t do contains your site’s Web handlers. our ApplicationState object. much but that you can modify to First, let’s look at some code from Let’s turn our attention to src/ start fleshing out your first project. Application.hs: Site.hs, which contains our appli- The snap init command creates cation’s Web handler code. The skele- the Main module for this project in type Application = SnapExtend ton application contains two example src/Main.hs. When you build this ApplicationState handlers. One answers requests to get project with cabal install, an the site’s root page; the other answers executable called myproject is cre- This line indicates that your applica- requests to /echo/foo by printing ated in $HOME/.cabal/bin. To build tion extends the Snap type (the type a message containing the foo input and run the example application, of basic Web handlers without any string (see Figures 3 through 5). execute these shell commands: associated in-memory state) with You can read this as, “If we’re JANUARY/FEBRUARY 2011 85 The Functional Web index = ifTop $ heistLocal (bindSplices indexSplices) $ render “index” This sets up a routing table for the where site’s URLs. Requests for the / URL indexSplices = are routed to the index handler; [ (“start-time,” startTimeSplice) requests for /echo/foo are routed , (“current-time,” currentTimeSplice) to the echo handler after we set ] stuff=foo in the request’s param- eter map. Figure 3. The root or homepage handler. This handler binds a couple of heist The site handler’s second half, template splices and renders the index template. after the main routing table, serves any files from the disk. Thea <|> b syntax means “try a; if it fails, try b.” In this case, if the user requests ... a URL that doesn’t match any of the <table id=”info”> routing-table entries — for exam- <tr> ple, /screen.css — the fileServe <td>Config generated at:</td> function tries to find the file under <td><start-time/></td> the resources/static directory </tr> and serves it back to the user if it’s <tr> found. If fileServe can’t find the <td>Page generated at:</td> file, the fileServe handler fails, <td><current-time/></td> causing the site handler to fail, </tr> which causes Snap to produce a “404 </table> Not Found” response. ... Benchmarks Figure 4. An example of splices in heist. The start-time/ and current- We compared Snap to five common time/ tags are bound to Haskell code, which renders HTML output. Web frameworks: Ruby on Rails 2.3.5 (using the internal server), Grails 1.2.2, Apache 2.2.16, PHP 5.2.14, and Node.js 0.2.4. echo = do Our comparison involved two message <- decodedParam “stuff” benchmarks, which we ran on a heistLocal (bindString “message” message) $ render “echo” quad-core Xeon machine running at where 2.33 GHz. The pong benchmark (see decodedParam p = fromMaybe <*> urlDecode <$> fromMaybe “” Figure 7a) is basically “Hello, World!” <$> getParam p It responds to requests by sending the string pong. (For the Apache/PHP Figure 5. The /echo handler. This code answers a request to /echo/foo by line in this figure, we used Apache printing a message containing the string foo. to serve the file and Apache with mod_php to issue the pong response.) The file benchmark (see Figure 7b) at the root page, bind the follow- resources/templates/index.tpl, measures how fast each server can ing HTML tags and render the index you can see these splices at work (see send a single 49-Kbyte image file.
Recommended publications
  • THE FUTURE of SCREENS from James Stanton a Little Bit About Me
    THE FUTURE OF SCREENS From james stanton A little bit about me. Hi I am James (Mckenzie) Stanton Thinker / Designer / Engineer / Director / Executive / Artist / Human / Practitioner / Gardner / Builder / and much more... Born in Essex, United Kingdom and survived a few hair raising moments and learnt digital from the ground up. Ok enough of the pleasantries I have been working in the design field since 1999 from the Falmouth School of Art and onwards to the RCA, and many companies. Ok. less about me and more about what I have seen… Today we are going to cover - SCREENS CONCEPTS - DIGITAL TRANSFORMATION - WHY ASSETS LIBRARIES - CODE LIBRARIES - COST EFFECTIVE SOLUTION FOR IMPLEMENTATION I know, I know, I know. That's all good and well, but what does this all mean to a company like mine? We are about to see a massive change in consumer behavior so let's get ready. DIGITAL TRANSFORMATION AS A USP Getting this correct will change your company forever. DIGITAL TRANSFORMATION USP-01 Digital transformation (DT) – the use of technology to radically improve performance or reach of enterprises – is becoming a hot topic for companies across the globe. VERY DIGITAL CHANGING NOT VERY DIGITAL DIGITAL TRANSFORMATION USP-02 Companies face common pressures from customers, employees and competitors to begin or speed up their digital transformation. However they are transforming at different paces with different results. VERY DIGITAL CHANGING NOT VERY DIGITAL DIGITAL TRANSFORMATION USP-03 Successful digital transformation comes not from implementing new technologies but from transforming your organisation to take advantage of the possibilities that new technologies provide.
    [Show full text]
  • Snap Creator Framework 4.3.3 Administration Guide
    Snap Creator® Framework 4.3.3 Administration Guide February 2021 | 215-14105_C0 [email protected] Snap Creator 4.3.3 Administration Guide ii Contents Contents What Snap Creator Framework does............................................................................ 6 Benefits of using Snap Creator....................................................................................................................................... 6 Snap Creator architecture...............................................................................................8 Snap Creator Server overview........................................................................................................................................ 8 Snap Creator Agent overview.......................................................................................................................................10 Plug-ins for application integration.............................................................................................................................. 11 Managing Snap Creator Server....................................................................................13 Starting, verifying, and stopping Snap Creator Server on Windows............................................................................ 13 Starting, verifying, and stopping Snap Creator Server on UNIX................................................................................. 13 Changing the Snap Creator Server port after installation.............................................................................................14
    [Show full text]
  • What I Wish I Knew When Learning Haskell
    What I Wish I Knew When Learning Haskell Stephen Diehl 2 Version This is the fifth major draft of this document since 2009. All versions of this text are freely available onmywebsite: 1. HTML Version ­ http://dev.stephendiehl.com/hask/index.html 2. PDF Version ­ http://dev.stephendiehl.com/hask/tutorial.pdf 3. EPUB Version ­ http://dev.stephendiehl.com/hask/tutorial.epub 4. Kindle Version ­ http://dev.stephendiehl.com/hask/tutorial.mobi Pull requests are always accepted for fixes and additional content. The only way this document will stayupto date and accurate through the kindness of readers like you and community patches and pull requests on Github. https://github.com/sdiehl/wiwinwlh Publish Date: March 3, 2020 Git Commit: 77482103ff953a8f189a050c4271919846a56612 Author This text is authored by Stephen Diehl. 1. Web: www.stephendiehl.com 2. Twitter: https://twitter.com/smdiehl 3. Github: https://github.com/sdiehl Special thanks to Erik Aker for copyediting assistance. Copyright © 2009­2020 Stephen Diehl This code included in the text is dedicated to the public domain. You can copy, modify, distribute and perform thecode, even for commercial purposes, all without asking permission. You may distribute this text in its full form freely, but may not reauthor or sublicense this work. Any reproductions of major portions of the text must include attribution. The software is provided ”as is”, without warranty of any kind, express or implied, including But not limitedtothe warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authorsor copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, Arising from, out of or in connection with the software or the use or other dealings in the software.
    [Show full text]
  • Carnivorous Plant Newsletter V44 N4 December 2015
    Technical Refereed Contribution Several pygmy Sundew species possess catapult-flypaper traps with repetitive function, indicating a possible evolutionary change into aquatic snap traps similar to Aldrovanda Siegfried R. H. Hartmeyer and Irmgard Hartmeyer • Weil am Rhein • Germany • s.hartmeyer@ t-online.de • www.hartmeyer.de Keywords: Drosera, pygmy Sundew, Aldrovanda, Dionaea, Droseraceae, Collembola, carnivorous plant, catapult-flypaper trap, snap trap, snap-tentacle, functional morphology, phylogeny. Abstract: Approximately 50 species of pygmy Sundews (genus Drosera, section Bryastrum) occur in the South of Australia and one each in New Zealand (D. pygmaea) and Venezuela (D. meristo- caulis). They grow mainly as small stemless rosettes possessing minute trapping leaves of 1-2 mm diameter with prominent marginal tentacles, or have elongated erect stems. The caulescent species possess only mucus-producing tentacles that are most effective in capturing small flying insects. The acaulescent species in contrast are specialized on crawling prey (Verbeek & Boasson 1993) and have developed mucus-free snap-tentacles (Fig. 1), able to bend surprisingly rapidly towards the leaf center. They lift prey like, e.g. springtails (Collembola) from the ground and carry it with a 180°-movement from the periphery of the plant onto the sticky leaf. Our examinations brought to light that several small species of section Bryastrum are able to catapult small animals even within fractions of a second. If the whole leaf is touched, several or even all marginal tentacles perform such bending movements simultaneously. We documented this behavior on video, featured on our film “Catapults in Pygmyland” on YouTube (www.youtube.com/watch?v=5k7GYGibdjM). Our results prove that more than only one species in the genus Drosera possess rapidly moving catapult-flypaper traps and that the examined pygmy catapults show a further specialization and function repeatedly (in contrast to the one-shot snap tentacles of D.
    [Show full text]
  • Analysing the Use of Outdated Javascript Libraries on the Web
    Updated in September 2017: Require valid versions for library detection throughout the paper. The vulnerability analysis already did so and remains identical. Modifications in Tables I, III and IV; Figures 4 and 7; Sections III-B, IV-B, IV-C, IV-F and IV-H. Additionally, highlight Ember’s security practices in Section V. Thou Shalt Not Depend on Me: Analysing the Use of Outdated JavaScript Libraries on the Web Tobias Lauinger, Abdelberi Chaabane, Sajjad Arshad, William Robertson, Christo Wilson and Engin Kirda Northeastern University {toby, 3abdou, arshad, wkr, cbw, ek}@ccs.neu.edu Abstract—Web developers routinely rely on third-party Java- scripts or HTML into vulnerable websites via a crafted tag. As Script libraries such as jQuery to enhance the functionality of a result, it is of the utmost importance for websites to manage their sites. However, if not properly maintained, such dependen- library dependencies and, in particular, to update vulnerable cies can create attack vectors allowing a site to be compromised. libraries in a timely fashion. In this paper, we conduct the first comprehensive study of To date, security research has addressed a wide range of client-side JavaScript library usage and the resulting security client-side security issues in websites, including validation [30] implications across the Web. Using data from over 133 k websites, we show that 37 % of them include at least one library with a and XSS ([17], [36]), cross-site request forgery [4], and session known vulnerability; the time lag behind the newest release of fixation [34]. However, the use of vulnerable JavaScript libraries a library is measured in the order of years.
    [Show full text]
  • DARPA and Data: a Portfolio Overview
    DARPA and Data: A Portfolio Overview William C. Regli Special Assistant to the Director Defense Advanced Research Projects Agency Brian Pierce Director Information Innovation Office Defense Advanced Research Projects Agency Fall 2017 Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) 1 DARPA Dreams of Data • Investments over the past decade span multiple DARPA Offices and PMs • Information Innovation (I2O): Software Systems, AI, Data Analytics • Defense Sciences (DSO): Domain-driven problems (chemistry, social science, materials science, engineering design) • Microsystems Technology (MTO): New hardware to support these processes (neuromorphic processor, graph processor, learning systems) • Products include DARPA Program testbeds, data and software • The DARPA Open Catalog • Testbeds include those in big data, cyber-defense, engineering design, synthetic bio, machine reading, among others • Multiple layers and qualities of data are important • Important for reproducibility; important as fuel for future DARPA programs • Beyond public data to include “raw” data, process/workflow data • Data does not need to be organized to be useful or valuable • Software tools are getting better eXponentially, ”raw” data can be processed • Changing the economics (Forensic Data Curation) • Its about optimizing allocation of attention in human-machine teams Distribution Statement “A” (Approved for Public Release, Distribution Unlimited) 2 Working toward Wisdom Wisdom: sound judgment - governance Abstraction Wisdom (also Understanding:
    [Show full text]
  • Cross-Platform Mobile Application for the Cothority
    Cross-Platform Mobile Application for the Cothority Vincent Petri & Cedric Maire School of Computer and Communication Sciences Decentralized and Distributed Systems Lab Semester Project January 2018 Responsible Supervisor Prof. Bryan Ford Linus Gasser EPFL / DeDiS EPFL / DeDiS 2 Acknowledgements We would like to express our special thanks to Linus Gasser who gave us the opportunity to do this very interesting project related to the collec- tive authority (Cothority) framework developed by the DeDiS laboratory at EPFL. We would like to thank him for the valuable help he gave us whenever we needed and for the knowledge he provided to us throughout the semester. Secondly, we would also like to thank our parents and friends who helped us through the hard times of finalising the project within the limited time frame. 3 1 Abstract The Cothority2 framework has been developed and maintained by the DeDiS laboratory at EPFL. This project provides a framework for develop- ing, analysing, and deploying decentralised and distributed cryptographic protocols. A set of servers that runs these protocols and communicates among each other is referred to as a collective authority, or cothority, and the individual servers are called cothority servers or conodes. A cothority that executes decentralised protocols could be used for collective signing, threshold signing, or the generation of public-randomness, to name only a few options. The highest level of abstraction can be created by protocols like the collective signature (CoSi) protocol, the random numbers (Rand- Hound) protocol, or the communication (Messaging) protocol used by the conodes to exchange data. Then come the services, which rely on these pro- tocols.
    [Show full text]
  • The Effect of Ajax on Performance and Usability in Web Environments
    The effect of Ajax on performance and usability in web environments Y.D.C.N. op ’t Roodt, BICT Date of acceptance: August 31st, 2006 One Year Master Course Software Engineering Thesis Supervisor: Dr. Jurgen Vinju Internship Supervisor: Ir. Koen Kam Company or Institute: Hyves (Startphone Limited) Availability: public domain Universiteit van Amsterdam, Hogeschool van Amsterdam, Vrije Universiteit 2 This page intentionally left blank 3 Table of contents 1 Foreword ................................................................................................... 6 2 Motivation ................................................................................................. 7 2.1 Tasks and sources................................................................................ 7 2.2 Research question ............................................................................... 9 3 Research method ..................................................................................... 10 3.1 On implementation........................................................................... 11 4 Background and context of Ajax .............................................................. 12 4.1 Background....................................................................................... 12 4.2 Rich Internet Applications ................................................................ 12 4.3 JavaScript.......................................................................................... 13 4.4 The XMLHttpRequest object..........................................................
    [Show full text]
  • Web Development Frameworks Ruby on Rails VS Google Web Toolkit
    Bachelor thesis Web Development Frameworks Ruby on Rails VS Google Web Toolkit Author: Carlos Gallardo Adrián Extremera Supervisor: Welf Löwe Semester: Spring 2011 Course code: 2DV00E SE-391 82 Kalmar / SE-351 95 Växjö Tel +46 (0)772-28 80 00 [email protected] Lnu.se/dfm Abstract Web programming is getting more and more important every day and as a consequence, many new tools are created in order to help developers design and construct applications quicker, easier and better structured. Apart from different IDEs and Technologies, nowadays Web Frameworks are gaining popularity amongst users since they offer a large range of methods, classes, etc. that allow programmers to create and maintain solid Web systems. This research focuses on two different Web Frameworks: Ruby on Rails and Google Web Toolkit and within this document we will examine some of the most important differences between them during a Web development. Keywords web frameworks, Ruby, Rails, Model-View-Controller, web programming, Java, Google Web Toolkit, web development, code lines i List of Figures Figure 2.1. mraible - History of Web Frameworks....................................................4 Figure 2.2. Java BluePrints - MVC Pattern..............................................................6 Figure 2.3. Libros Web - MVC Architecture.............................................................7 Figure 2.4. Ruby on Rails - Logo.............................................................................8 Figure 2.5. Windaroo Consulting Inc - Ruby on Rails Structure.............................10
    [Show full text]
  • CS 683 Emerging Technologies Fall Semester, 2006 Doc 23 Rails 7 AJAX Nov 16, 2006
    CS 683 Emerging Technologies Fall Semester, 2006 Doc 23 Rails 7 AJAX Nov 16, 2006 Copyright ©, All rights reserved. 2006 SDSU & Roger Whitney, 5500 Campanile Drive, San Diego, CA 92182-7700 USA. OpenContent (http:// www.opencontent.org/opl.shtml) license defines the copyright on this document. References script.aculo.us, Common Ajax Javascript library, http://script.aculo.us/ Surveying open-source AJAX toolkits, Peter Wayner, Inforworld, July 31, 2006, http://www.infoworld.com/article/ 06/07/31/31FEajax_1.html Proprietary AJAX toolkits: The other side of the coin, Peter Wayner, Inforworld, July 31, 2006, http://www.infoworld.com/ infoworld/article/06/07/31/31FEajaxsb_1.html Ajax/DHTML Library Scorecard:How Cross Platform Are They? Musings from Mars ,March 4th, 2006, http:// www.musingsfrommars.org/2006/03/ajax-dhtml-library-scorecard.html Wikipedia, http://en.wikipedia.org/wiki/Main_Page Agile Web Development with Rails 2nd Ed Bl.16 October 25, Thomas & Hanson, The Pragmatic Bookshelf, PDF Rails API, http://api.rubyonrails.org/ Some Ajax Reading Why Ajax Sucks (Most of the Time) Jacob Nielson http://www.usabilityviews.com/ajaxsucks.html Ajax SWik http://swik.net/Ajax Ajax Mistakes How to use XMLHttpRequest Places to use Ajax 2 Web Browsers suck for developing applications HTML is very limited as UI Delay in response from server 3 Reducing Suckiness CSS Javascript XMLHttpRequest 4 Cascading Style Sheets - CSS stylesheet language that describes layout of HTML & XML Provides HTML better control over layout body { background-color: #fff;
    [Show full text]
  • The Haskell Cabal
    The Haskell Cabal A Common Architecture for Building Applications and Tools Isaac Jones Simon Peyton Jones Simon Marlow Malcolm Wallace Ross Patterson The Haskell Library and Tools Infrastructure Project is an effort to provide a framework for developers to more effectively contribute their software to the Haskell community. This document specifies the Common Architecture for Building Applications and Tools(Cabal), which contributes to the goals of the Haskell Library and Tools Infrastructure Project. Specifically, the Cabal describes what a Haskell package is, how these packages interact with the language, and what Haskell implementations must to do to support packages. The Cabal also specifies some infrastructure (code) that makes it easy for tool authors to build and distribute conforming packages. The Cabal is only one contribution to the Library Infrastructure project. In particular, the Cabal says nothing about more global issues such as how authors decide where in the module name space their library should live; how users can find a package they want; how orphan packages find new owners; and so on. The Cabal has been discussed by the implementors of GHC, Nhc98, and Hugs, all of whom are prepared to implement it. The proposal is now open for wider debate. Please contribute by emailing <[email protected]>. 1 The Haskell Cabal 1. The Haskell Package System: goals The Haskell Package System (Cabal) has the following main goal: to specify a standard way in which a Haskell tool can be packaged, so that it is easy for consumers to use it, or re-package it, regardless of the Haskell implementation or installation platform.
    [Show full text]
  • Marian Edu, Acorn IT About Me
    Chatbots & OpenEdge Marian Edu, Acorn IT About me Working with Progress since 1998 4GL & OO, AppServer Architecture & Integration Java, .NET node.js, javascript, typescript angular, nativescript Chatbots & OpenEdge acorn.ro Chatbot A chatbot is a computer program or an artificial intelligence which conducts a conversation via auditory or textual methods. Such programs are often designed to convincingly simulate how a human would behave as a conversational partner, thereby passing the Turing test. Wikipedia Chatbots & OpenEdge acorn.ro Chatbot & AI Natural Processing Language. Semantic vs. Linguistic Model Keyword matching. Don’t really need to pass the Turing test. Chatbots & OpenEdge acorn.ro Usage Virtual Assistants. Messaging Apps. Organisation Apps/Websites. Chatbots & OpenEdge acorn.ro Use Cases Customer Support. e-Commerce. Marketing, news, finance, etc... Chatbots & OpenEdge acorn.ro Skip Theory Assistants Alexa Skills Kit Actions on Google Messaging Integration. OpenEdge Integration. Chatbots & OpenEdge acorn.ro Assistants Understanding User Input NPL, AI, Intents, Workflow IBM Watson Assistant Amazon Alexa Google Assistant Chatbots & OpenEdge acorn.ro Assistants REST Services (PAAS – subscription) JSON payload Intent/Workflow definition (designer) API’s Chatbots & OpenEdge acorn.ro Smart Speakers Speech Recognition Amazon – Echo, Echo dot, Echo Plus, Echo Spot, Echo Auto… Google – Google Home, Mini, Max Facebook – Portal (Alexa) Chatbots & OpenEdge acorn.ro Amazon Alexa Alexa Console – Skills and Intents Fulfilment
    [Show full text]