Decentralized applications (DApps) gained traction in the context of the blockchain technology. Ethereum is currently the public blockchain that backs the largest amount of the existing DApps. Onboarding new users to Ethereum DApps is a... more
Decentralized applications (DApps) gained traction in the context of the blockchain technology. Ethereum is currently the public blockchain that backs the largest amount of the existing DApps. Onboarding new users to Ethereum DApps is a notoriously hard issue to solve. This is mainly caused by lack of cryptocurrency ownership, needed for transaction fees. Several meta-transaction patterns emerged for decoupling users from paying these fees. However, such solutions are mostly offered via off-chain, often paid relayer services and do not fully address the security issues present in the meta-transaction path. In this paper, we introduce a new meta-transaction architecture that makes use of the Intel Software Guard Extensions (SGX). Unlike other solutions, our approach would offer the possibility to deploy a fee-free Ethereum DApp on a web server that can directly relay meta-transactions to the Ethereum network while having essential security guarantees integrated by design.
Abstract Multidatabase serializability is defined as an extension of the well-known serializability theory in order to provide a theoretical framework for research in concurrency control of transactions over multidatabase systems. Also... more
Abstract Multidatabase serializability is defined as an extension of the well-known serializability theory in order to provide a theoretical framework for research in concurrency control of transactions over multidatabase systems. Also introduced are multidatabase serializability graphs which capture the ordering characteristics of global as well as local transactions. Two schedulers that produce multidatabase serializable histories are described. The first scheduler is a conservative one which only permits one global ...
In this paper, we present the mechanisms needed for Byzantine fault tolerant coordination of Web services atomic transactions. The mechanisms have been incorporated into an open-source framework implementing the standard Web services... more
In this paper, we present the mechanisms needed for Byzantine fault tolerant coordination of Web services atomic transactions. The mechanisms have been incorporated into an open-source framework implementing the standard Web services atomic transactions specification. The core services of the framework, namely, the activation service, the registration service, the completion service, and the distributed commit service, are replicated and protected with our Byzantine fault tolerance mechanisms. Such a framework can be useful for many transactional Web services that require high degree of security and dependability.
Preface. How This Document Is Organized. Related Publications. International Technical Support Organization Publications. International Technical Support. Organization on the World Wide Web. International Technical Support Organization on... more
Preface. How This Document Is Organized. Related Publications. International Technical Support Organization Publications. International Technical Support. Organization on the World Wide Web. International Technical Support Organization on the Internet. VisualAge Support on CompuServe. About the Authors. Acknowledgments. 1. VISUALAGE AND TRANSACTIONAL OBJECTS. 1. Client/Server Environment. IBM's Client/Server Strategy: Open Blueprint. Focus on Customers. Focus on Servers. Open Blueprint. Benefits. Services. Choosing the Services to Use. Evolution of Client/Server Computing. Future of Open Blueprint. Object Management Group. 2. Client/Server Models. Distributed Presentation. Remote Presentation. Distributed Function. Remote Data Management. Distributed Data Management. 3. VisualAge Frameworks and Transaction Processing. VisualAge End-User Application Architecture. VisualAge Classes and Parts. Business Logic within Visual Parts. Business Logic within Nonvisual Parts. Implementing Business Logic. End-user Application Architecture Using Business Agents. VisualAge Communications Framework. Dialog Layer. System Layer. System Interface Layer. 4. Objects and Procedural Data Structures. Overview of Implementation Classes. AbtCompoundType. Responsibility. Creating an AbtCompoundType. AbtRecord. Responsibility. Creating an AbtRecord. Creating an AbtRecord Nonvisual Part. AbtForeignRecord. Responsibility. Creating an AbtForeignRecord. OSStruct. Responsibility. Creating an OSStruct Subclass. Expanding the Object Boundary into the Procedural World. Creating Business Agents. Defining Business Actions for Business Agents. 2. VISUALAGE TRANSACTION PROGRAMMING. 5. VisualAge Sample Applications. Overall Approach. Basic Procedural Applications. Common Data Record. Scope of Each Chapter. 6. VisualAge CICS Implementation. Overview. CICS Transaction Samples. CICS Intercommunication Functions. Function Shipping. Distributed Program Link. VisualAge Implementation of CICS Parts. Simple CICS Transaction Sample. Coding. Testing: Locally with CICS OS/2. Testing: Function Shipping to CICS/MVS. Testing: Distributed Program Link to CICS/MVS. Testing: Distributed Program Link to CICS/MVS and Function Shipping. CICS Proc Dialog Parts and Attributes. ProcDialog (AbtCICSProcDialog). fileRec (fileRec). connectionSpec (AbtCICSConnectionSpec). connection (AbtCICSOS2Transaction). LUWToken (Integer). lastError (AbtCICSOS2Error). Advanced Transaction Sample: CICS Logical Unit of Work. CICS Logical Unit of Work. LUW Terms. LUW Management Issues. CICS Logical Unit of Work (AbtCICSOS2Transaction). FileRecAbtForeignRecord (AbtForeignRecord). CICS Program (AbtCICSProgram). The Dream ATM Application. Prototyping. Developing. Application Architecture. ITSCAccountNV. ITSCCheckingAccountNV. ITSCSavingAccountNV. ITSCLogonPswNV. ITSCAccountView. ITSCCheckingAccountView. ITSCSavingAccountView. ITSCATMMainView. ITSCLogonPswView. ITSCAccountAbtForeignRecord. ITSCCheckingAccountCICS. ITSCSavingAccountCICS. ITSCCICSErrorView. Design Considerations. Pool Dictionary for Security. Defining Attributes of an Agent. Assigning Instance Variables to a Subpart. No Primary Subpart for Nonvisual Parts. Execution of a CICS Request. Logical Unit of Work per Agent. Multiple CICS Requests. CICS Error Handling. Merging Data Structures. Logical Unit of Work. Distributed Program Link. Using the COMMAREA. 7. VisualAge APPC Implementation. APPC Overview. What Is APPC? Terminology. Typical Transaction Flows. Inquiry Transaction (Request and Reply). Credit Check Transaction (Confirmed Delivery). File Transfer (Batch Send). Database Update Transaction (Conversational Reply). VisualAge Implementation of APPC Parts. Simple APPC Transaction Sample. Coding. Testing. APPC Proc Dialog Parts and Attributes. ProcDialog (AbtAPPCProcDialog). fileRec (fileRec). connectionSpec (AbtAPPCConnectionSpec). connection (AbtAPPCConversation). lastError (AbtAPPCError). aReception (AbtAPPCReception). Advanced Transaction Sample: APPC Multiple-Receive Dialog. Coding. Testing. 8. VisualAge TCP/IP Implementation. Overview. TCP/IP Protocol Suite. Sockets. Stream- and Record-Oriented Protocols. VisualAge Implementation of TCP/IP Parts. Simple TCP/IP Transaction Sample. Coding. Testing. TCP Proc Dialog Parts and Attributes. ProcDialog (AbtTCPProcDialog). fileRec (fileRec). connectionSpec (AbtTCPConnectionSpec). connection (AbtSocket). lastError (AbtTCPError). Advanced Transaction Sample: TCP/IP Stream Dialog. Coding. Testing. APPENDICES. A. Multitype Record Class Generator Tool. Problem Description. Installation under VisualAge Team. User's Guide. Invoking the Tool. Generated Classes. Use. Merging Data Structures by Use of a Buffer. AbtBuffer and AbtReusableBuffer. Generating the Individual Data Structure. Changes to ITSCCheckingAccountCICS. B. Communications Setup. Installation Checklist. APPC Setup Process. Communications Manager/2 Setup. Configuration. Network Definition File. CICS/ESA Setup Process. VTAM. CICS…
