Experimental Physics and
Industrial Control System
| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 <2004> 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 <2004> 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: buying tornado seats for EPICS application developers |
| From: | Matthias Clausen <[email protected]> |
| To: | EPICS tech-talk <[email protected]> |
| Date: | Fri, 30 Jan 2004 09:38:03 +0100 |
Does this not really come back to the question which license is necessary just to be allowed to use the Tornado header files? - And why?I am in the process of renewing our vxWorks maintenance. Unfortunately, WRS still does not have a two tier licensing scheme for users of Tornado GUI tool verses folks that are just building and installing executables with scripts (i.e. typical EPICS application developers).
In any case isn't it enough to have one license in house to compile anything?
As far as I can see our developers here we just use the GUI tools to generate new Tornado images. Debugging on the target is not used. Therefore we've already reduced the number of developer seats.
Again - why would an application developer need a seat? Isn't one license enough? The number of seats limits the number of concurrent developer/ online debugging sessions. Is the number of developers using the header files limited?It occurs to me that there is a potential to significantly reduce the cost of Tornado ownership at EPICS installations. It seems that if someone were to modify the SNL compiler so that it produced byte code which is interpreted at run time (similar to JAVA) and there was an option to create an alternative IOC configuration where dependence on the target symbol table by vxWorks compiled iocCore was removed (we already have this working on other OS with R3.14), then the application developer wouldn't need to use a Tornado seat.
On the other hand I like the idea to look into the byte code option:
Why similar to Java? Why not running a Java VM on the IOC?
What are the chances and the risks doing that - and which other licenses might be necessary? Applications with high demand in functionality and low performance might benefit from the Java approach.
And - there's only one byte code running anywhere.
Comments?
Sites might need to buy Tornado seats for building EPICS base and forWe are working on the same problem and heard a similar rumor in Germany.
developing drivers, but not for developing EPICS function block databases or
to develop SNL based logic.
I was just curious if there was any general level of interest in that
approach?
P.S. I just heard that there is a new 8k US $ per year per seat licensing model from WRS which allows unlimited use of any hostArch / targetArch / project permutation by one user.
We hope that the service contract for this year might already be based on such an approach.
-Matthias
- References:
- buying tornado seats for EPICS application developers Jeff Hill
- Navigate by Date:
- Prev: Re: buying tornado seats for EPICS application developers Till Straumann
- Next: Re: buying tornado seats for EPICS application developers D. Peter Siddons
- Index: 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 <2004> 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024
- Navigate by Thread:
- Prev: Re: buying tornado seats for EPICS application developers D. Peter Siddons
- Next: RE: buying tornado seats for EPICS application developers Hunt Steven
- Index: 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 <2004> 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·