W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > August 2012

[Bug 18610] New: Transferable should expose a close() method

From: <bugzilla@jessica.w3.org>
Date: Fri, 17 Aug 2012 22:21:09 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-18610-2532@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18610

           Summary: Transferable should expose a close() method
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Web Messaging (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: glenn@zewt.org
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org


Every Transferable object is neuterable.  Neutering is useful in cases other
than transferring.

For example, being able to programmatically neuter a large ArrayBuffer when
you're finished performing computations in it would be useful, to give the UA
the option of freeing the memory associated with it immediately instead of
waiting for GC.

Any object big enough for Transferable to be useful (aside from MessagePort,
which is a minor anomaly) is also big enough for close() to be useful.  Instead
of APIs handling this one by one, this should simply be supported for all
Transferables.

This should be no burden for any API supporting Transferable, since they
already have to do the work of implementing the "neuter" concept.

(MessagePort already has a close() method.  It would be nice if its behavior
could be aligned with Transferable.close(), so they can be the same method.)

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 17 August 2012 22:21:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 17 August 2012 22:21:11 GMT