How lilydjwg/morerssplz works
Main Components
a. Web Server Layer
• Main request handler (from base.py)
• Static file serving component (for index.html)
b. Feed Processors Layer
• Zhihu (专栏 & 动态)
• V2EX
• Telegram
• Gogs
• Matters
• Jike
• Each processor should be represented as a module with clear input/output flows
c. External Services Layer
• External APIs being accessed:
• Zhihu API
• V2EX API
• Telegram API
• Other source APIs
d. Caching Layer
• Caching mechanism (indicated by cache_hit/cache_miss metrics)
• Queue management system (referenced by queue_full metric)
e. Monitoring/Metrics Layer
• StatsD integration
• Timing and count metrics collection points
Component Relationships
[Client Requests] → [Tornado Web Server]
• ↓
[Static Content] ← [Request Handler] → [StatsD Monitoring]
• ↓
• [Feed Processors]
• ↙ ↓ ↘
• [Zhihu] [V2EX] [Telegram] ...
• ↓ ↓ ↓
• [Cache Layer]
• ↓ ↓ ↓
[External APIs/Services Layer]
Additional Notes
• Version requirements (Python 3.5+, Tornado 5+)
• External dependencies (PyRSS2Gen, lxml, pycurl)
• Optional proxy support interface point
Key Metrics to Highlight
• morerss.zhihu.fetch (timing)
• morerss.handler.Handler.Code (timing)
• morerss.zhihu.queue_full (count)
• morerss.zhihu.cache_hit/miss (count)