Mirabito RLM Pt.2 - Eniz Ozden; Korkut Balta; Muhammad Selim Albayrak;

Week 1: 02/14/2025

Accomplishments:

• Gave a presentation to project managers detailing our current status and outlining what needs to be done for the work ahead.

To-Do:

• Define the project scope.
• Work on Capture and Auth requests.

Week 2: 02/19/2025

Objectives and Tasks:

• Development Environment Configuration:

 - Set up the C#/.NET environment.  
 - Configure the TCP server and integrate XML parsing tools.

• Resource Access:

 - Access Mirabito Lab resources.  
 - Retrieve relevant log files, if available.

• TCP Listener Development:

 - Develop an initial TCP listener capable of accepting and storing XML messages from POS devices.

• Connectivity Testing:

 - Conduct basic connectivity tests using simulated POS requests.

• Logging Mechanism Implementation:

 - Establish a comprehensive logging system to capture all incoming messages for further analysis.

Week 3: 02/26/2025

Objectives and Tasks:

• Message Processing:

 - Develop XML parsing logic to extract key elements from AUTH and CAPTURE messages.  
 - Implement handlers for AUTH and CAPTURE messages.
 - Implement Forwarding mechanism to capture correct response form the production server

• Response Handling:

 - Develop a response generator to construct appropriate XML responses.

• System Validation:

 - Conduct tests with sample message flows to verify server functionality to achieve correct response 

• Expected Outcomes:

 - A working system capable of processing AUTH and CAPTURE requests and generating appropriate responses.

• Deliverables:

 - Functional XML parser and message handlers
 - Implementation of response generation logic.

Week 4: 03/05/2025

Objectives and Tasks:

• Frontend Development:

- Implement SendStatusRequest, SendAuthRequest, and SendCaptureRequest to send valid STATUS → AUTH → CAPTURE requests.
- Develop ProcessStatusResponse, ProcessAuthResponse, and ProcessCaptureResponse to parse and validate incoming responses.
- Modularize message sending with AddLengthPrefix, and unify receiving logic with ReceiveMessage.

• Sequence Handling:

- Enforce correct message sequence: STATUS → AUTH → CAPTURE.
- Store AUTH response (e.g., CPERID, RewardID) for CAPTURE request construction.

• Testing:

- Verify client logic by observing communication using Wireshark.
- Confirm prefix length format and proper server response to each message.

• Expected Outcomes:

- A complete client capable of sending and interpreting STATUS, AUTH, and CAPTURE messages correctly.

• Deliverables:

- Final version of FrontendClient.cs with modular, tested methods.