Re: async

Hi Samu,

It was an interesting discussion on Wednesday, thanks for following up here.
As Ruben said, Stream spec was intended for async processing, including very large streams. 

I would find it useful if you could shortly describe *the interface you wish to have* and how would you use it in some specific scenario of your choice. While everyone could use one's imagination, I think having a concrete example could help in focusing the discussion.

Best,
elf Pavlik


On Wednesday, March 25th, 2026 at 3:55 PM, Samu Láng <langsamu@hotmail.com> wrote:

> Why are none of the methods in RDF/JS asynchronous and could we make them such?
> 
> In a recent discussion of the Solid Open-source Tools group (whose members tend to be heavily invested in both RDF and JavaScript), I had asked whether I was the only one struggling with the lack of asynchronicity in RDF/JS. Specifically I mean asynchronicity in the sense of the `async` and `await` keywords in JavaScript, of methods that return `Promise`s. As an implementer of software that adheres to the RDF/JS: Data model specification and the RDF/JS: Dataset specification, I frequently come up against the problem of using synchronous methods like `DatasetCore.match` in contexts that favor it nowadays like network IO and background processing.. My fellow implementers/users of RDF/JS reported that they struggle with the same issue and tend to go through hoops to make RDF/JS work in 'modern' context.
> 
> My question is generic and open: Was there any thought given to this? Was it discarded? Or have we just come some way since? How would we go on about adding asynchronicity to RDF/JS? Is there history worth reading about the topic?
> 
> I have searched the mailing list and GitHub for relevant information and haven't found any. I apologize if I'm reopening a long dormant debate and would appreciate pointers to previous discussion.

Received on Thursday, 26 March 2026 14:01:33 UTC