Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Editing Newsreader/enhancing salvo newsreader/Porting Existing NNTP Implementation

Revision as of 07:48, 22 August 2012 by Unnamed Poltroon (Talk) (New page: == Abstract == Proting the existing implementation to newly invented features was a challenge. There were lot to change and many aspects to think of. Always the UI should be generic and ...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Abstract

Proting the existing implementation to newly invented features was a challenge. There were lot to change and many aspects to think of. Always the UI should be generic and protocol dependent implementations should not reside in UI classes. Clear seperation between back-end and front-end is always expected.

Work Done

In the earlier Salvo implementation Server(changed as NNTPServer in our context) is created at the UI level as soon as useer enters the user information. But initializing a protocol dependant server cannot be done at UI level since we have to always check for protocol type before creating Server. So it will result in lot of if elses. Solution was to implement a generic Server. This server implementation just serve the purpose of information passing. It is a very lower level implementation with fewer methods since it is generic. This server will be converted to a protocol dependent concrete form once the container of perticulat protocol type is initialized. setServer(IServer server) method of container can be used to extract the details from generic container and then initialize protocol dependent servert(Ex:NNTPServer)

<<Under Construction>>

Back to the top