After getting a better understanding of the number of security holes that must be plugged in order to make JNEXT safe for deployment on public Web sites, it seems this is definitely not going to be a walk in the park. Ironically, The power and flexibility of JavaScript, which motivated me to create JNEXT in the first place, is the very reason that makes the task of letting JNEXT loose on the Web a very difficult one.

Since at this point, there are not many people actively involved in developing JNEXT, my dilemma is whether to spend more time researching how to make JNEXT's security watertight or to forget about Web deployment for now, define JNEXT as a tool for rapid application development and concentrate on creating cool extensions for it.

Anyone care to comment ?

[ add comment ] ( 5 views )   |  permalink  |   ( 3 / 72 )

---

<Back | 1 | 2 | 3 | 4 | 5 | 6 | 7 | Next> Last>>

No Footer - Page Generated in 0.2642 seconds | Site Views: 12501