How excoffierleonard/parser works
Main Components
a) Client Layer:
• Web Frontend (Static files: HTML, CSS, JS)
• External API Clients
b) Web Service Layer:
• HTTP Server (parser-web crate)
• Route Handlers
• /parse endpoint
• /hello endpoint
• static file serving
c) Core Parser Layer (parser-core crate):
• Document Parsers
• PDF Parser
• DOCX Parser
• XLSX Parser
• PPTX Parser
• Text Parser
• Image Parser (OCR)
d) External Dependencies:
• Tesseract OCR Engine
• File Format Libraries
[Client Layer] → [Web Service Layer] → [Core Parser Layer]
Important Relationships
• HTTP request flow from clients to web service
• File data flow through the system
• Error propagation paths
• Integration with Tesseract OCR
• Configuration influence on components
Additional Details
• Environment variable configuration points
• Docker container boundary
• Test coverage areas
Implementation Notes
• Version information for major components
• Scalability points
Remember to include:
• Clear entry points for both web UI and API clients
• The relationship between parser-web and parser-core crates
• The role of the Tesseract OCR engine
• Error handling paths
• Configuration points
• Docker container boundary
• Test coverage areas
This will provide a complete picture of how the service processes files while maintaining a clear separation of concerns between the web interface and core parsing functionality.