How talalalha/vehicfinder-cpit305-project works
Project type and purpose
• VehicFinder is a Java-based, console-driven car-search application with two operating modes:
• Local mode: reads car data from a CSV file (or local database) and filters results in-process.
• Server/Client mode: runs a server that holds the data and business logic, and one or more clients that connect over TCP to request filtered results.
• It uses Maven for build, JDK 11+, optional MySQL (or other JDBC) database, and simple socket networking.
File structure
• Top-level artifacts:
• pom.xml – Maven build, dependencies, packaging.
• CleanedCarData.csv – source of car data for local mode.
• src/main/java/IO/CSVReader.java – CSV file parsing.
• src/main/java/db/… – domain model (Cars), persistence (DatabaseConnection), controller (CarsController), Main launcher.
• src/main/java/Networking/Server.java & Client.java – TCP server and client entry points.
• src/main/java/org/example/App.java – console UI/menu logic.
• Tests mirror each package under src/test/java.
• No external microservice definitions, so it’s a single monolithic codebase with two run profiles.
README for additional insights
• Confirms two modes: local and server/client.
• Workflow: user inputs filters → application reads data → applies filters → presents results.
• In server/client: the client shows the same prompts but forwards them to the server over port 9000.
3. Split beneath into two paths:
– Server/Client path: