<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-07-31T11:45:36Z</responseDate>
  <request identifier="6117" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:6117</identifier>
        <datestamp>2024-03-06T10:38:01Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>Transactional Tasks: Parallelism in Software Transactions</dc:title>
          <dc:creator>Swalens, Janwillem</dc:creator>
          <dc:creator>De Koster, Joeri</dc:creator>
          <dc:creator>De Meuter, Wolfgang</dc:creator>
          <dc:subject>Concurrency</dc:subject>
          <dc:subject>Parallelism</dc:subject>
          <dc:subject>Futures</dc:subject>
          <dc:subject>Threads</dc:subject>
          <dc:subject>Fork/Join</dc:subject>
          <dc:subject>Software Transactional Memory</dc:subject>
          <dc:description>Many programming languages, such as Clojure, Scala, and Haskell, support different concurrency models.&#13;
In practice these models are often combined, however the semantics of the combinations are not always well-defined.&#13;
In this paper, we study the combination of futures and Software Transactional Memory.&#13;
Currently, futures created within a transaction cannot access the transactional state safely, violating the serializability of the transactions and leading to undesired behavior.&#13;
&#13;
We define transactional tasks: a construct that allows futures to be created in transactions.&#13;
Transactional tasks allow the parallelism in a transaction to be exploited, while providing safe access to the state of their encapsulating transaction.&#13;
We show that transactional tasks have several useful properties: they are coordinated, they maintain serializability, and they do not introduce non-determinism.&#13;
As such, transactional tasks combine futures and Software Transactional Memory, allowing the potential parallelism of a program to be fully exploited, while preserving the properties of the separate models where possible.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Janwillem Swalens and Joeri De Koster and Wolfgang De Meuter</dc:contributor>
          <dc:date>2016</dc:date>
          <dc:relation>Is Part Of LIPIcs, Volume 56, 30th European Conference on Object-Oriented Programming (ECOOP 2016)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/LIPIcs.ECOOP.2016.23</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-61173</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/LIPIcs.ECOOP.2016.23</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by/3.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
