Protection! Licensing Toolkit 4.2 released
Join the DZone community and get the full member experience.
Join For Free
jproductivity has released
protection!
4.2
, a greatly improved version of leading licensing solution for software developer and publishers.
protection! provides a complete turnkey licensing package that lets software vendors lock pirates out of their copyrighted software.
this
release
introduces stability improvements for the protection! framework and localization to additional 7 (seven) new languages. new features and usability advancements for
protection! enterprise
include: better time zones support; ability to control license delivery to free emails domains (i.e., hotmail.com); additional views allowing drill-down into specific customer and license details; improved dynamic filtering allowing for faster and more precise searches; new approaches in contacting customers from within protection! enterprise other minor improvements and fixes.
protection! licensing toolkit
v4.2 is a suite of products covering wide range of vendors' licensing and intellectual property protection needs.
"the new protection! lets software vendors quickly add licensing into their applications and use protection! enterprise as a turnkey solution to fully automate day-to-day licensing activities," said gregory ledenev, cto of jproductivity.
protection! licensing toolkit empowers software developers to implement robust licensing features into their applications, while providing a friendly and non-invasive environment to their end-users.
protection! 4 has been verified for windows 2000/2003/xp/vista/2008, solaris/sparc, linux (red hat/suse/debian/ubuntu), and mac os x. for more detailed information about features, upgrade policies and pricing please visit: http://www.jproductivity.com/
see protection! in action:
http://www.jproductivity.com/products/protection/screenshots.htm
trial versions
of the entire protection! licensing toolkit family are available for
download
from the
company's web site.
Opinions expressed by DZone contributors are their own.
Comments