[ease-dev] Bug 511888

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[ease-dev] Bug 511888

From: Prash D <prashanthd912@xxxxxxxxx>
Date: Sun, 5 Mar 2017 16:25:05 +0530
Delivered-to: ease-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/ease-dev>
List-help: <mailto:ease-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/ease-dev>, <mailto:ease-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/ease-dev>, <mailto:ease-dev-request@eclipse.org?subject=unsubscribe>

Hi Christian,

It's related to Bug 511888.

Is Synchronization a good solution to this problem? However I read it comes with several problems. One includes possibility of performance reduction and second creation of deadlocks. Will these two cases be relevant in this type of code?

Prashanth

Follow-Ups:
- Re: [ease-dev] Bug 511888
  - From: Jonah Graham

Prev by Date: [ease-dev] Introduction
Next by Date: Re: [ease-dev] Bug 511888
Previous by thread: [ease-dev] Introduction
Next by thread: Re: [ease-dev] Bug 511888
Index(es):
- Date
- Thread

Breadcrumbs