John:

> 1.  Does this project set a precedent in that we now
>     expect projects to provide KDE hooks?  If so then
>     what are the said hooks?

To be honest, I was unsure about whether we should distribute this file
since we do not yet support KDE on Solaris.  I do not have strong feelings
about whether it should be included or not.  I would be happy to remove it
if ARC feels we should wait until KDE is more supported before including
such files.  Codina will still work for KDE users, it just will not
automatically inform the users about plugin updates without the KDE
specific desktop file.  However, after receiving the update email, a KDE
user could run codeina by hand to do the update, or just follow the steps
in the email and download it via a web browser.

> 2.  How does this project deal with a user who switches
>     between SPARC and x86?  How does this project deal 
>     with a user who switches their Sun Ray server via 
>     utswitch?  What if the server was SPARC and is now x86?
>     Are the implications of this that the user would have 
>     to purchase a new plugin?  Would the difference in 
>     system architecture cause the application to fail?
>     Would the difference in system architecture cause the
>     mechanism to overwrite the previous version?

When you use the codeina application to login to the Fluendo server, you
register your username and are given a password.  Users can then freely
re-download plugins that have been previously purchased.  This is useful if
the user accidently deletes the plugin or if the plugin has been updated (in
which case the user should receive an email and codeina should automatically
prompt the user to upgrade).

However, each plugin license is only valid for one computer, so the user is
expected to not abuse the license they agreed to when purchasing the plugin.
In other words, users agree to not install the plugin on multiple machines.
When a user replaces one machine with another, it is okay to migrate the
license from one machine to another, as long as the same plugin license is
not used on both.

I will need to check with Fluendo if purchasing an x86 plugin allows you to
migrate to a Sparc plugin (or a plugin for a different distro for that
matter) in the future, or if users need to buy a new set of plugins when
switching from x86 to Sparc or vice versa.  I will respond when I get an
answer.

Brian

Reply via email to