Henry Wong wrote:
surlac surlacovich wrote:
Siddique Ansari wrote:I am making a desktop application which will be running on multiple PC's sharing the same Database. Should I use Socket programming? Please suggest me What to do?
I see no way to avoid socket programming if you talking about PCs in network. JDBC will use sockets under the hood anyway.
I believe the context of the question was in regards to "socket programming" -- not whether sockets are used "under the hood". If the DB is the only service that communicates with the applications, then JDBC alone could do the job. Otherwise, you will need some sort of network based communications, and yes, the socket library is probably the simplest choice.
jagrutkumar dalwadi wrote:By looking at your error it seems that it is servlet configuration issue.
Correct configuration would be as below:
Reason: If we are putting "/" before url pattern, container understands that request should start from the servlet context. However that we dont want in this case.