4 Commits

Include renames

Author	SHA1	Message	Date
Admin Bot	ef79bf9a80	merge: resolve conflicts with main ... - Keep workflow internal handler (JSON-to-gRPC bridge) - Keep notification internal handler with X-Resource routing - Remove dead Handle* methods replaced by ServeHTTP - Fix describe/list resource specs (correct upstream paths) - Restore GetWorkflowSpec() function	2026-09-15 15:13:42 +09:00
Admin Bot	db8f103fa5	fix: workflow dispatcher uses internal handler instead of raw gRPC proxy ... - Wire WorkflowAdapter as internal handler (JSON-to-gRPC bridge) - Add ServeHTTP to WorkflowAdapter: maps X-Resource to Temporal action - Rename resource 'start' to 'execute' for consistency - Add GET methods for describe/list/history resources - Remove unused workflowAdapterImpl variable - SDK clients can now send JSON, gateway translates to gRPC	2026-09-15 13:33:33 +09:00
3 people	30e0a83a50	feat(network): SSE optimization for local LLM streaming (#31 #32 #33) (#26) ... Addresses three critical network issues for LLM streaming performance: **#33 Disable proxy buffering for SSE** - Add X-Accel-Buffering: no header to response - Tells nginx/Ingress to stream events immediately instead of buffering **#32 HTTP/2 multiplexing for concurrent streams** - Enable HTTP/2 in server config via http2.ConfigureServer() - Increase MaxConnsPerHost to 10 for better concurrency - Allows multiple concurrent LLM requests without blocking **#31 TCP backpressure for streaming LLM responses** - Set TCP_NODELAY on dialer to disable Nagle's algorithm - Reduces latency by sending small packets immediately - Critical for low TTFT (time-to-first-token) under load **Tests added:** - TestTCPBackpressure: Verifies TCP backpressure handling with slow client - TestConcurrentSSEStreams: Confirms HTTP/2 multiplexing works correctly --------- Co-authored-by: poison <[email protected]> Reviewed-on: #26 Co-authored-by: poimen <[email protected]>	2026-09-13 23:37:33 +00:00
Admin Bot	c6cd41fd4b	feat: implement WorkflowAdapter with namespace pass-down support ... Enable X-Service: workflow routing to Temporal via ServiceAdapter. Users can now specify namespace/domain in request payload for multi-tenant workflow access. Changes: - Implement WorkflowAdapter in serviceadapter/workflow_adapter.go * Defines 10 workflow resources: start, describe, list, history, terminate, cancel, signal, query, reset, update * Each resource validates namespace parameter in payload * Forwards requests to Temporal gRPC handler - Add GetWorkflowSpec() to define ServiceAdapter spec with: * Upstream: grpc://temporal:7233 * Auth requirements per operation (execute, read, signal, query) * Request/response schemas for validation - Wire WorkflowAdapter into main.go: * Register workflow adapter in serviceadapter registry * Initialize with temporal handler for gRPC forwarding - Remove old empty WorkflowAdapter stub from adapters.go Usage: curl -X POST https://api.riotpiao.com/ \ -H 'X-Service: workflow' \ -H 'X-Resource: start' \ -H 'Authorization: Bearer TOKEN' \ -d '{ "namespace": "default", "workflow_id": "my-workflow", "workflow_type": "MyWorkflow", "task_queue": "default" }' Namespace is required in all workflow operations and must be specified by the client in the request payload. This enables multi-tenant support where different teams access their own Temporal namespaces.	2026-09-14 08:21:49 +09:00