fransiskus
New Member
Currently consolidating multiple legacy PASOE services into single backend (~160 endpoints). Constraint: environment prevents using .cls OOABL. Entire backend must stay 100% procedural .p code and .i includes. Almost every modern PASOE example pushes OOABL classes and WebHandler inheritance. Looking for battle-tested patterns from teams running pure .p REST setups in production: 1. Routing: How do you dispatch cleanly? Thin WebHandler calling RUN VALUE(...) into domain .p files? Central dispatcher .p parsing URL path manually? Or stick to REST transport? 2. Session hygiene: Running session-free without class destructors: how do you prevent agent sessions leaking temp-table data, dirty NO-LOCK buffers, or state across reused sessions? 3. JSON handling: For nested payloads, DATASET ... WRITE-JSON vs building responses via Progress.Json.ObjectModel? Any memory leak gotchas under concurrent load? Curious what patterns hold up best under high load.
