[TIMOB-9178] Tooling: Enforce ti.verify for javascript modules
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2012-05-30T09:08:38.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Tooling |
| Labels | n/a |
| Reporter | Jeff English |
| Assignee | Neeraj Gupta |
| Created | 2012-05-20T12:52:10.000+0000 |
| Updated | 2017-03-22T21:14:49.000+0000 |
Description
We need to be able to support ti.verify on javascript (commonJS and MobileWeb) modules. This is a requirement for some of the enterprise-related modules that we are developing. In addition, module developers would like to put their javascript modules on the MarketPlace with ti.verify being used to confirm authorization to use the module.
We require more information for this ticket. In the context of this request, does commonJS refer to: * Modules compiled from commonJS only for a specific system (i.e. prebuilt modules which are javascript implementations) * Modules which are raw javascript only
These tickets are for raw javascript only files. For example, the ti.cloud module is a raw javascript file in the commonjs folder. This is coming from community as well as internal needs to be able to package a single javascript module (commonjs) that can be used on all platforms.
So the module will be completely in plaintext? That's what a CommonJS module that isn't compiled is. There's no way we can guarantee IP protection with that, although we could verify based on SHA1 hash.
Native JS module support has recently been added to Android so this is no longer a valid feature request.
Closing ticket as invalid with reference to the above comments.