tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kranti™ K K Parisa <>
Subject Re: Securing Tomcat Applications from Reverse Engineering
Date Thu, 21 Jan 2010 15:14:51 GMT
Well there are soo many comments on the cost of IP and other tools. when we
are a small team started working on a web based product with open source
tools, for sure we can't spend too much on the tools to protect the IP
rights. because once we deploy for few clients, if its a good product, what
if they steal the code and also ideas. i agree to have legal terms and all
that stuff. but that would be a big story for us being small.

so just wanted to see if anything available to protect our work, ideas
(ideas at code implementation level by using different opensource
technologies, well there are many companies who started like this).

anyways thanks for the comments, i would love to share if we invent anything
in this process, because small is big and it matters :)

Best Regards,
Kranti K K Parisa

On Thu, Jan 21, 2010 at 5:00 PM, André Warnier <> wrote:

> Peter Crowther wrote:
>> 2010/1/21 Kranti™ K K Parisa <>
>>> How could we achieve this without the above tool? Because the pricing of
>>> the
>>> above tool is very costly.
>>> Well, you could always spend the developer-years to create your own
>>> version
>> of that tool... which would probably be *more* costly.
> I'll add something to that, just for the sake of it.
> I personally find this situation ironic : here we have someone who wants to
> protect their own code, presumably so that they can charge the customer for
> a copy of it, in order to get back their cost of development and some
> justified profit for their work.
> But the same people are apparently unwilling to pay for a product that
> would allow them to do so, and is sold on the same terms.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message