Originally posted by rathi ji:
Hi,
Please suggest me a Java Project, should not be a web project. College level, 2 months duration.
Thanks.
![]()
Originally posted by KJ Reddy:
You can try converting any web project into swing based desktop application
Originally posted by Kailash Thiyagarajan:
You can make a three tier application using Swings, RMI and JDBC. Create a database, use a Swing client where the Label values of the widgets can be configured according to a properties file (or an XML file and use a SAX parser). Use RMI as the middle tier to call the JDBC classes.
Initially the application can be specific to a particular business such as a Stock market and then once it's built, try to make the application generic so that it can be used be used for basic Cruds operation. That should take about 2 months or more for a student.
Originally posted by rathi ji:
Good advice. But I haven't worked on RMI and I feel, duration is short to learn RMI and then develop. Could you please suggest something which doesn't include RMI and EJB...
Any good project related to Networking (Socket Programming), Multi-Threading...
Thanks a lot.
![]()
[ February 14, 2006: Message edited by: rathi ji ]
But I haven't worked on RMI and I feel, duration is short to learn RMI and then develop.
Originally posted by Vishnu Prakash:
Learn RMI if you are planning to develop a distributed application.
For 2 months college project desktop based MVC would be the best choice.
Originally posted by Pradip Bhat:
Write a chat application that sends encrypted messages.I involves UI, networking, encryption algorithm and multithreading.
Can you please elaborate bit more desktop based MVC projects. If possible give me some examples.
Originally posted by Svend Rost:
Hi Rathi,
Do you have any ideas yourself? and does the project have any requirements
with respect to technologies?
Ok, my idea..
JavaRanch's Stage Coach System:
-------------------------------
Techonologies: Threads, GUI (Swing pref.) and Sockets
Design Patterns: MVC, Observer/Observable
The Ranch's has a number of monitors which displays some
information about the X next stagecoaches to arrive at the Ranch. The
Monitors get their information from a Server.
Use Swing (or AWT) and the MVC pattern for the monitors. Each monitor is
an observer which enlists to the Server. You'll use Socket communication
between the Server and the Monitors.
So? how about that...
/Svend Rost
[ February 15, 2006: Message edited by: Svend Rost ]
Originally posted by rathi ji:
Yes, I am thinking about File Download Accelerator. It will (can) improve the file download (transfer) speed.
...
Originally posted by rathi ji:
About your idea, I am not sure I understood it or not...
Originally posted by rathi ji:
did you mean that, each client will access server for different-different kinds of information and will display it i.e. one client will display the number of online user, other will display number of total user etc...and all the client will get this information from server... I am not sure, but it looks like *web project*...
Originally posted by Svend Rost:
Does the above have anything with my project suggestion to do? Umm..
assuming you, by client, mean monitor/oberserver then they won't access
the server for information as they are observers (read: http://www.exciton.cs.rice.edu/JavaResources/DesignPatterns/ObserverObservable.htm)
It looks like a web project? It's not, you can make the project in J2SE
and install the "monitor software" on a number of different machines, and
let them get a connection (socket) to a server which will publish data to
the monitors, which then will display the data.
/Svend Rost
Originally posted by rathi ji:
But I think, it is implementation of observer pattern in a *swing & networking* way... looks small... may be I am wrong here.
Originally posted by Svend Rost:
Dont know if it's small - depends on your expirienceA decent java
programmer can do the above in one day, a student with no expirience
in Swing and network programming might have to use longer time.
If it's for Uni, then I think in general it's better to choose a small
project, rather than a big one. You can always add functionality.