1 / 19

Design Paradigm

Design Paradigm. Transparent to the user Component add-on rather than alteration GINI remains independent Only altered the Configuration file. David El Achkar, Simon Foucher , Mia Hochar, Marc Atie. Design Paradigm. Use of flexible communication library: twisted GINI already in Python

moral
Download Presentation

Design Paradigm

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. Design Paradigm • Transparent to the user • Component add-on rather than alteration • GINI remains independent • Only altered the Configuration file David El Achkar, Simon Foucher, Mia Hochar, Marc Atie

  2. Design Paradigm • Use of flexible communication library: twisted • GINI already in Python • Flexible • Available source code • Stable • High-level functions David El Achkar, Simon Foucher, Mia Hochar, Marc Atie

  3. Improvements Overview Client Server Workers Front End Dispatcher Back End Database Back End Back End Scheduler Back End David El Achkar, Simon Foucher, Mia Hochar, Marc Atie

  4. Current Access to remote server

  5. Connection to server

  6. Front End Connection to server SSH Tunnel • Back End

  7. Addition to GINI

  8. Addition to GINI

  9. Gateway to the cloud

  10. Sequence of Events 1. Send Dummy variable NoWorker Front End Dispatcher Database David El Achkar, Simon Foucher, Mia Hochar, Marc Atie

  11. Sequence of Events 2. Dispatcher searches for a worker Front End Dispatcher Best Worker? Database David El Achkar, Simon Foucher, Mia Hochar, Marc Atie

  12. Sequence of Events 3. Returns worker or dummy variable Front End Dispatcher Worker’s IP Database David El Achkar, Simon Foucher, Mia Hochar, Marc Atie

  13. Why the dummy variable? • Need to establish TCP communication • Recycled as an error flag • Could be user to convey info in future upgrade

  14. End Result: Unaltered GINI

  15. Front End Connection to server SSH Tunnel • Hidden location of back end • Back End

  16. Flexibility • Non-fixed data types being passed • Currently a string: IP, DNS or anything else

  17. Drawback • Temporary TCP connection: Port expiration at timeout • Most Clients don’t have DNS

  18. Design Dilemma • Either • Maintain permanent client-dispatcher connection • Resources consuming • Might not bring any benefits • Requires heavy alterations to gServer • Drop the connection after delivering the goods • Lightweight component • No resources used • Impossible (or difficult) to retrieve clients

More Related