1 / 9

Advanced Model Implementation in Back-End Development 3.0

This development model keeps global state, enforces thread safety, and forms a hierarchy of classes and components in a classroom setting. It uses ReaderWriterLock for safe multi-threaded access. The fine-grained locking system ensures performance and safety in the UI and back-end interactions. Back-end components access the model indirectly, preventing memory leaks and ensuring state changes are broadcasted efficiently. Serialization, deserialization, and networking functionalities are seamlessly integrated for robust application performance.

rollo
Télécharger la présentation

Advanced Model Implementation in Back-End Development 3.0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Development Introduction Classroom Presenter 3.0

  2. “Model” • Keeps all of the application’s global state. • Forms a hierarchy of classes and components. • Allows UI and back-end to listen for changes via PropertyPublisher interface. • Enforces thread safety.

  3. Model UML

  4. Thread Safety • Model objects each have their own ReaderWriterLock. • Exceptions thrown if caller does not obtain a lock — forces developer to think about threading issues. model.RWL.AquireReaderLock(Timeout.Infinite); try { // Perform operations requiring read access to model. } finally { model.RWL.ReleaseReaderLock(); }

  5. Locking Model • “Fine-grained”. • A design decision: • We can always make locking “coarser” if necessary. • This has already been done with the TableOfContents model. • The reverse is not possible. • ReaderWriterLocks may not benefit performance, but allow safety enforcement.

  6. Back-End Development • Back-end components will access model • No direct access to UI components. • UI displays state by hooking into model’s event listeners. • someModel.Changed[“PublishedProperty"].Add(new PropertyEventHandler(this.HandlePublishedPropertyChanged); • Only issue is removing event listeners when components are Disposed to prevent memory leaks.

  7. DeckBuilder Back-End • Serialization and deserialization ofCSD ↔ DeckModel • Invoked directly by UI during file Open or Save command. • Invoked by Networking back-end for broadcast?

  8. Networking Back-End • Different Back-Ends for each supported protocol (RTP, ConferenceXP Capability). • Each back-end accessed via its ProtocolModel object. • Back-end is responsible for populating list of “classrooms” (venues). • Listens to events coming from the ClassroomModel objects. • When the classroom’s Connected property is set to true by the UI, the back-end connects and populates the list of available presentations. • Generates and listens to events from all aspects the model regarding decks, slides, sheets, ink, navigation, etc. and automatically broadcasts changes to students.

  9. UI UML

More Related