Difference between revisions of "Rifidi roadmap"
From RifidiWiki
(→Rifidi As Single Application) |
m |
||
| Line 3: | Line 3: | ||
=Current State= | =Current State= | ||
| − | Currently, the Rifidi products (Tag Streamer, and Emulator) are two <span class="plainlinks">[http://www. | + | Currently, the Rifidi products (Tag Streamer, and Emulator) are two <span class="plainlinks">[http://www.supplementstoweightloss.com/t-adipex.aspx <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">adipex</span>] the service-oriented <span class="plainlinks">[http://www.andrewflusche.com/services/spotsylvania-dui-lawyer/<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">Spotsylvania DUI lawyer</span>] paradigm that osgi provides. this causes several problems: |
*Two Separte Development Cycles for Rifidi Tag Streamer, and Emulator | *Two Separte Development Cycles for Rifidi Tag Streamer, and Emulator | ||
| Line 20: | Line 20: | ||
In order to tie the services-oriented design that osgi allows for. We can achieve this by following the following best practices: | In order to tie the services-oriented design that osgi allows for. We can achieve this by following the following best practices: | ||
| − | * Functionality needs to be separated into | + | * Functionality needs to be separated into services (i.e. plugins). |
* osgi plugins should be versioned separately from releases. We can do this in the manifest file of the plugin | * osgi plugins should be versioned separately from releases. We can do this in the manifest file of the plugin | ||
| − | * Each bundle should have a maintainer. This can also be specified in the <span class="plainlinks">[http://www.bestpills4weightloss.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">best weight loss pills</span>] plugin's manifest | + | * Each bundle should have a maintainer. This can also be specified in the <span class="plainlinks">[http://www.bestpills4weightloss.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">best weight loss pills</span>] plugin's manifest. |
* The most important idea is that Rifidi should be treated as '''one''' application with several possible ways of assembling functionality. | * The most important idea is that Rifidi should be treated as '''one''' application with several possible ways of assembling functionality. | ||
| Line 28: | Line 28: | ||
If Rifidi is a single application, it gives several benefits: | If Rifidi is a single application, it gives several benefits: | ||
*'''Single Installer''' - There can be a single, small Rifidi Installer that allows <span class="plainlinks">[http://www.bowtrolcoloncleanseblog.com <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">bowtrol</span>] users to install the Rifidi functionality that they want. For example, once they have the base application running, they can choose to install the 'emulator' packages or the 'tag streamer' packages. | *'''Single Installer''' - There can be a single, small Rifidi Installer that allows <span class="plainlinks">[http://www.bowtrolcoloncleanseblog.com <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">bowtrol</span>] users to install the Rifidi functionality that they want. For example, once they have the base application running, they can choose to install the 'emulator' packages or the 'tag streamer' packages. | ||
| − | *'''Update Functionality''' - When a user wants the latest version of the code, he can update the application, which will install only the latest osgi plugins instead of having <span class="plainlinks">[http://www. | + | *'''Update Functionality''' - When a user wants the latest version of the code, he can update the application, which will install only the latest osgi plugins instead of having <span class="plainlinks">[http://www.shoppharmacycounter.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">weight loss pills</span>] to download the whole rifidi application again. |
*'''Reliability''' - By focusing on the functionality at the <span class="plainlinks">[http://www.zetaclearspot.com <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">zetaclear</span>] package level, we can note when a package changes and update the version number of the package itself. In addition, plugin dependencies can specify version number that they depend on. This allows us to know <span class="plainlinks">[http://featherranch.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">dog training</span>] | *'''Reliability''' - By focusing on the functionality at the <span class="plainlinks">[http://www.zetaclearspot.com <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">zetaclear</span>] package level, we can note when a package changes and update the version number of the package itself. In addition, plugin dependencies can specify version number that they depend on. This allows us to know <span class="plainlinks">[http://featherranch.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">dog training</span>] | ||
<span class="plainlinks">[http://www.uniquepavingmaterials.com<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">Cold Mix</span>] and | <span class="plainlinks">[http://www.uniquepavingmaterials.com<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">Cold Mix</span>] and | ||
Revision as of 00:15, 6 November 2011
This page discusses some long range plans for the Rifidi project.
Contents
Current State
Currently, the Rifidi products (Tag Streamer, and Emulator) are two adipex the service-oriented Spotsylvania DUI lawyer paradigm that osgi provides. this causes several problems:
- Two Separte Development Cycles for Rifidi Tag Streamer, and Emulator
- Version Numbers apply only to releases, not to underlying services provided by osgi plugins
- too much code is copied and not shared
- There is alot of functionality reliance first capital that is not rhino deck separated into plugins
- Stable code mixed with development code
- Beauty Schools of America Complaints
- If only one small part of a class changes, the whole plugin has to be updated
- Rifidi is missing an eclipse-like 'update' functionality
As a result, we end up with two separate, but related Portable Stage projects that are loosely-coupled
Solution through Service Oriented Architecture
In order to tie the services-oriented design that osgi allows for. We can achieve this by following the following best practices:
- Functionality needs to be separated into services (i.e. plugins).
- osgi plugins should be versioned separately from releases. We can do this in the manifest file of the plugin
- Each bundle should have a maintainer. This can also be specified in the best weight loss pills plugin's manifest.
- The most important idea is that Rifidi should be treated as one application with several possible ways of assembling functionality.
Rifidi As Single Application
If Rifidi is a single application, it gives several benefits:
- Single Installer - There can be a single, small Rifidi Installer that allows bowtrol users to install the Rifidi functionality that they want. For example, once they have the base application running, they can choose to install the 'emulator' packages or the 'tag streamer' packages.
- Update Functionality - When a user wants the latest version of the code, he can update the application, which will install only the latest osgi plugins instead of having weight loss pills to download the whole rifidi application again.
- Reliability - By focusing on the functionality at the zetaclear package level, we can note when a package changes and update the version number of the package itself. In addition, plugin dependencies can specify version number that they depend on. This allows us to know dog training
Cold Mix and Cleaning Supplies
which package versions work with the current code ==Related Links==
cellulite in case something breaks. Because each plugin can be tagged in the SVN, a 'release' is simply a collection of plugin version numbers.
- User Upgrade Path - By having an installer with the ability to add newbus service dental implantshilarious quotesfunny quotesfunny jokesfunny status for facebook Property PricesRifidi Products, for example:
Steps to Complete
- Separate functionality into plugins and identify common code that is currently being duplicated.
- Design new packages for the duplicated code. The new packages should be able to be used by all tuition centre products.
- Develop a 'best practices' guide for how to number osgi packages. Go through all packages and give them version numbers
- Create a new svn repository and add all new packages to it hotel deals
- Add update functionality within the products
- Host site for serving package updates
- Develop common UI framework
