On Fri, Feb 4, 2011 at 11:13 AM, Rui Miguel Silva Seabra <[email protected]> wrote:
> Em 04-02-2011 09:36, Cedric BAIL escreveu:
>> On Fri, Feb 4, 2011 at 10:14 AM, Rui Miguel Silva Seabra<[email protected]>  
>> wrote:
>>> Em 04-02-2011 08:27, Cedric BAIL escreveu:
>>>> On Thu, Feb 3, 2011 at 6:26 PM, Rui Miguel Silva Seabra<[email protected]>
>>>>   wrote:
>>>>> Em 25-01-2011 05:36, Ian Caldwell escreveu:
>>>>>> Lets hear your thoughts...
>>>>>
>>>>> Thread safety for ecore!
>>>>
>>>> Ecore already provide facility to handle thread, thread safety are
>>>> really not needed. But Efreet mime type could really be thread safe
>>>> that would be highly usefull !
>>>
>>> How do you make two downloads in the background at the same time, then?
>>
>> ecore_con_url handle that already for you. It would be a waste of
>> ressource to have one download per thread, as you basically just watch
>> one fd per download.
>
> Ok, shouldn't that pass to ecore_con then?
>
> Discomfitor told me ecore_con is not thread safe as a reason I can't
> have multiple Azy actions, so I have to have generic functions and
> disable network operations in the UI while one Azy action is in place,
> and then enable them again at the end.
>
> This sucks a bit, I would love to allow people to post messages with Azy
> while Azy downloads in the "background"...

That's sounds more like an issue in Azy design than with ecore_con.
Sadly I don't know much about it. So Discomfitor, explain to us what
is going on here !?
-- 
Cedric BAIL

------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to