Reactive Internet programming : (Record no. 357)
[ view plain ]
| 000 -LEADER | |
|---|---|
| fixed length control field | 06197nam a2200601 i 4500 |
| 001 - CONTROL NUMBER | |
| control field | 011452872585 |
| 005 - DATE AND TIME OF LATEST TRANSACTION | |
| control field | 20260528133338.0 |
| 006 - FIXED-LENGTH DATA ELEMENTS--ADDITIONAL MATERIAL CHARACTERISTICS | |
| fixed length control field | m eo d |
| 007 - PHYSICAL DESCRIPTION FIXED FIELD--GENERAL INFORMATION | |
| fixed length control field | cr cn |||m|||a |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION | |
| fixed length control field | 160511s2016 nyua fob 000 0deng d |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| International Standard Book Number | 9781970001778 |
| Qualifying information | ebook |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| Canceled/invalid ISBN | 9781970001785 |
| Qualifying information | ePub |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| Canceled/invalid ISBN | 9781970001761 |
| Qualifying information | paperback |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| Canceled/invalid ISBN | 9781970001792 |
| Qualifying information | hardcover |
| 024 7# - OTHER STANDARD IDENTIFIER | |
| Standard number or code | 10.1145/2872585 |
| Source of number or code | doi |
| 035 ## - SYSTEM CONTROL NUMBER | |
| System control number | (OCoLC)949774405 |
| 040 ## - CATALOGING SOURCE | |
| Original cataloging agency | CaBNVSL |
| Language of cataloging | eng |
| Description conventions | rda |
| Transcribing agency | CaBNVSL |
| Modifying agency | CaBNVSL |
| 050 #4 - LIBRARY OF CONGRESS CALL NUMBER | |
| Classification number | QA76.625 |
| Item number | .B277 2016 |
| 082 04 - DEWEY DECIMAL CLASSIFICATION NUMBER | |
| Classification number | 005.276 |
| Edition information | 23 |
| 035 ## - SYSTEM CONTROL NUMBER | |
| System control number | (CaBNVSL)swl00406470 |
| 100 1# - MAIN ENTRY--PERSONAL NAME | |
| Personal name | Barbier, Franck., |
| Relator term | author. |
| 245 10 - TITLE STATEMENT | |
| Title | Reactive Internet programming : |
| Remainder of title | State Chart XML in action / |
| Statement of responsibility, etc. | Franck Barbier. |
| 250 ## - EDITION STATEMENT | |
| Edition statement | First edition. |
| 264 #1 - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE | |
| Place of production, publication, distribution, manufacture | [New York] : |
| Name of producer, publisher, distributor, manufacturer | Association for Computing Machinery ; |
| Place of production, publication, distribution, manufacture | [San Rafael, California] : |
| Name of producer, publisher, distributor, manufacturer | Morgan & Claypool, |
| Date of production, publication, distribution, manufacture, or copyright notice | 2016. |
| 300 ## - PHYSICAL DESCRIPTION | |
| Extent | 1 PDF (xv, 224 pages) : |
| Other physical details | illustrations. |
| 336 ## - CONTENT TYPE | |
| Content type term | text |
| Source | rdacontent |
| 337 ## - MEDIA TYPE | |
| Media type term | electronic |
| Source | isbdmedia |
| 338 ## - CARRIER TYPE | |
| Carrier type term | online resource |
| Source | rdacarrier |
| 490 1# - SERIES STATEMENT | |
| Series statement | ACM books, |
| International Standard Serial Number | 2374-6777 ; |
| Volume/sequential designation | #10 |
| 504 ## - BIBLIOGRAPHY, ETC. NOTE | |
| Bibliography, etc. note | Includes bibliographical references (pages 223-224). |
| 506 ## - RESTRICTIONS ON ACCESS NOTE | |
| Terms governing access | Abstract freely available; full-text restricted to subscribers or individual document purchasers. |
| 588 ## - SOURCE OF DESCRIPTION NOTE | |
| Source of description note | Title from PDF title page (viewed on May 11, 2016). |
| 538 ## - SYSTEM DETAILS NOTE | |
| System details note | Mode of access: World Wide Web. |
| 538 ## - SYSTEM DETAILS NOTE | |
| System details note | System requirements: Adobe Acrobat Reader. |
| 505 0# - FORMATTED CONTENTS NOTE | |
| Formatted contents note | 1. Introduction -- 1.1 Software engineering in the Internet era -- 1.2 Expected benefits of model-driven software development -- 1.3 Programming with events and states -- 1.4 Model execution or interpretation -- 1.5 Architectural issues of Internet programming -- |
| 505 8# - FORMATTED CONTENTS NOTE | |
| Formatted contents note | 2. Event and state-based modeling and programming -- 2.1 States are universal and everywhere -- 2.2 States are abstract and discrete -- 2.3 "Event" as dual notion of state -- 2.4 -- Harel's Statecharts -- 2.5 Discovering state chart XML -- 2.6 Statechart execution -- |
| 505 8# - FORMATTED CONTENTS NOTE | |
| Formatted contents note | 3. Applying State Chart XML -- 3.1 Startup of Barbados crisis management system -- 3.2 Business case: "route negotiation" -- 3.3 Timing constraints -- 3.4 Introduction to the run-to-completion execution mode -- 3.5 Variations on modeling: the power of Statecharts -- 3.6 Evaluation -- |
| 505 8# - FORMATTED CONTENTS NOTE | |
| Formatted contents note | 4. Programming State Chart XML models -- 4.1 Programming "my device" -- 4.2 Setup of entry and exit actions -- 4.3 Setup of activities -- 4.4 Sending events internally -- 4.5 Action parameters -- 4.6 State machine kick-off -- 4.7 State machine shutdown -- 4.8 State machine tracing -- 4.9 Transition programming -- 4.10 Guard programming -- 4.11 Event processing -- 4.12 Communication programming -- |
| 505 8# - FORMATTED CONTENTS NOTE | |
| Formatted contents note | 5. Execution semantics -- 5.1 Example of execution semantics potential defects -- 5.2 Run-to-completion cycles -- 5.3 Action and activity execution sequencing -- 5.4 Execution sequencing and orthogonality -- 5.5 Execution sequencing and nesting -- 5.6 Event consumption principle -- 5.7 Deferred events -- 5.8 Transition conflicts -- |
| 505 8# - FORMATTED CONTENTS NOTE | |
| Formatted contents note | 6. Advanced programming with PauWare engine -- 6.1 Completion transitions -- 6.2 Timer services -- 6.3 State and event naming -- 6.4 Single nesting -- 6.5 The notion of "internal transition" in State Chart XML -- 6.6 Allowed events at large -- 6.7 Unicast vs. multicast calls/communications -- 6.8 Cached transitions vs. contextual transitions -- 6.9 Data consistency checking through state invariants -- 6.10 History facilities -- 6.11 Concurrency -- |
| 505 8# - FORMATTED CONTENTS NOTE | |
| Formatted contents note | 7. Programming the "Internet of things" -- 7.1 Characterization of "Internet of things" applications -- 7.2 Application requirements (home automation system) -- 7.3 Analysis -- 7.4 Design -- 7.5 Implementation issues -- |
| 505 8# - FORMATTED CONTENTS NOTE | |
| Formatted contents note | 8. Programming web enterprise applications -- 8.1 Characterization of web enterprise applications -- 8.2 Application requirements (railcar control system) -- 8.3 Analysis -- 8.4 Design -- 8.5 Implementation issues -- |
| 505 8# - FORMATTED CONTENTS NOTE | |
| Formatted contents note | 9. Software component management -- 9.1 Dynamical (Re)configuration -- 9.2 Extended management framework -- 9.3 Pushing state machine data outside -- |
| 505 8# - FORMATTED CONTENTS NOTE | |
| Formatted contents note | Appendix A. Internal structure of PauWare engine -- A.1. Organization of a state machine's states in memory -- A.2. Organization of a state machine's transitions in memory -- Appendix B. Acronyms -- Appendix C. Downloadable software resources -- References -- Author's biography. |
| 520 3# - SUMMARY, ETC. | |
| Summary, etc. | Is Internet software so different from "ordinary" software? This book practically answers this question through the presentation of a software design method based on the State Chart XML W3C standard along with Java, Web enterprise, Internet-of-Things, and Android applications, in particular, are seamlessly specified and implemented from "executable models." Internet software puts forward the idea of event-driven or reactive programming, as pointed out in Bon�er et al.'s "Reactive Manifesto" (http://www.reactivemanifesto.org). It tells us that reactiveness is a must. However, beyond concepts, software engineers require effective means with which to put reactive programming into practice. This book's purpose is to outline and explain such means. The lack of professional examples in the literature that illustrate how reactive software should be shaped can be quite frustrating. Therefore, this book helps to fill in that gap by providing in-depth professional case studies that contain comprehensive details and meaningful alternatives. Furthermore, these case studies can be downloaded for further investigation. Internet software requires higher adaptation, at run time in particular. After reading Reactive Internet Programming, the reader therefore will be ready to enter the forthcoming Internet era. |
| 530 ## - ADDITIONAL PHYSICAL FORM AVAILABLE NOTE | |
| Additional physical form available note | Also available in print. |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM | |
| Topical term or geographic name entry element | Internet programming. |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM | |
| Topical term or geographic name entry element | SCXML (Document markup language) |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM | |
| Topical term or geographic name entry element | Statecharts (Computer science) |
| 776 08 - ADDITIONAL PHYSICAL FORM ENTRY | |
| Relationship information | Print version: |
| International Standard Book Number | 9781970001792 |
| -- | 9781970001761 |
| 830 #0 - SERIES ADDED ENTRY--UNIFORM TITLE | |
| Uniform title | ACM books ; |
| Volume/sequential designation | #10. |
| International Standard Serial Number | 2374-6777 |
| 856 48 - ELECTRONIC LOCATION AND ACCESS | |
| Materials specified | Abstract with links to full text |
| Uniform Resource Identifier | <a href="http://dx.doi.org/10.1145/2872585">http://dx.doi.org/10.1145/2872585</a> |
No items available.