XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Using XML (or JSON) for inter-thread communication



On 19/03/2012 14:44, Andrew Welch wrote:
> On 19 March 2012 14:36, John Cowan<cowan@mercury.ccil.org>  wrote:
>> Andrew Welch scripsit:
>>
>>> As far as I know, as we all move towards functional programming we
>>> won't have to worry too much about it as it gets taken care of for us.
>> Good luck with that.
> Is that not the case?
>
Things get better, but the problem shifts.

For example, the next Saxon release will automatically do 
multi-threading for xsl:result-document (each output document is 
produced in parallel with the others). But I had a test case the other 
day where doing everything at the same time blew the heap, so I had to 
suppress the multi-threading in order to conserve memory. Automating the 
resource trade-offs is the next level, but with diminishing returns I 
don't know if it will ever happen. So users still need to know what's 
going on and turn the dials occasionally.

Michael Kay
Saxonica


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS