> But the point I was trying to make is that everytime you change your > deisgn or release a new "version" of your electronic device you have to > re-apply for the ISO standard and pay fees again to get the certification.
ah - yes i see your point - fees. Yes this is just like that. Every time you change something you have to reapply (and pay). and yes that is a killer for us small developers. I wonder what this means for custom software? If we develop an application for a single customer and they want to run it on a "palladium secure" box do we have to recertify every time we fix a bug? (Sounds like a good argument for breaking things into servlettes). Can the components be certified separately? (Time for me to RTFM on this i see). this is where the level of control the sysadmin will have really matters. I do wish some group (like ISO) had come out with a competing standard ALREADY so MS didn't have the initiative on this one. -ns http://www.roserox.co.th --------------------------------------------------------------------------- New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] Website: http://www.delphi.org.nz To UnSub, send email to: [EMAIL PROTECTED] with body of "unsubscribe delphi" Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
