L
Luke Webber
I am in the planning stage for a Java-based business app, and my present
thinking is that I will have the UI as a thick client delivered via
Java Webstart, and communicating to the database via JDBC, with
Hibernate over the top of that. Pretty simple, which I like.
But now for the problem. The clients are likely to want to expose at
least parts of the app via the Web for /their/ clients to use. Now I can
either do this by writing that part of the system twice, once in Java
and once as a web app using JSP, or I can try to design this thing so
that it can be delivered over the web without compromising data
security. Hence this question.
Obviously, exposing a database to the internet is not a great idea. A
bit like exposing your dangly bits in a pub brawl. So what are my
alternatives here?
Many thanks for any and all suggestions, flames or kicks in the goolies.
Luke
thinking is that I will have the UI as a thick client delivered via
Java Webstart, and communicating to the database via JDBC, with
Hibernate over the top of that. Pretty simple, which I like.
But now for the problem. The clients are likely to want to expose at
least parts of the app via the Web for /their/ clients to use. Now I can
either do this by writing that part of the system twice, once in Java
and once as a web app using JSP, or I can try to design this thing so
that it can be delivered over the web without compromising data
security. Hence this question.
Obviously, exposing a database to the internet is not a great idea. A
bit like exposing your dangly bits in a pub brawl. So what are my
alternatives here?
Many thanks for any and all suggestions, flames or kicks in the goolies.
Luke