Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource Knowledge Stream Contributor An entity responsible for making contributions to the resource Lawrence Catania Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource *ponders* thread and process architecture Description An account of the resource Process Architecture Philosophy (Isolation & Protection) Core Idea: Each process is a distinct, independent world with its own virtual memory, file handles, and resources. Focus: Security, stability, and fault containment (one process crashing doesn't affect others). When to Use: Running separate applications (e.g., browser tabs, different software). Tasks requiring high security or running untrusted code. When tasks are heavy and don't need frequent shared data. Trade-off: Slower communication (IPC needed) and heavier context switching (saving/restoring entire memory maps). Thread Architecture Philosophy (Sharing & Concurrency) Core Idea: Threads are lightweight sub-tasks within a single process, sharing the same memory, code, and resources. Focus: Responsiveness, efficiency, and easy data sharing for concurrent operations. When to Use: Performing multiple tasks within one application (e.g., UI updates while downloading). CPU-bound tasks that benefit from parallelism on multi-core systems. Trade-off: Lack of built-in isolation; requires careful synchronization (locks, mutexes) to prevent race conditions and data corruption.