mirror of https://gitee.com/pnoker/iot-dc3.git synced 2026-11-04 15:24:51 +08:00

Files

T

pnoker 769d1cb977 style: apply repository-wide formatting

- expand single-line Javadocs to multi-line blocks, rewrap Markdown prose, and reflow POM, YAML, and TypeScript formatting
- formatting only: no Java code lines changed, no build-file semantics changed
- verified: backend compile and check_documentation.py pass, pnpm check and pnpm lint:check pass, and the dc3 YAML files parse

2026-08-25 13:35:00 +08:00

src/main/protobuf/api/common/data

feat(tsdb): rewire the data center onto the tsdb port and retire the repository module

2026-08-20 21:58:01 +08:00

pom.xml

refactor(api): reorganize proto files from center to common package

2026-07-09 12:43:48 +08:00

README.md

style: apply repository-wide formatting

2026-08-25 13:35:00 +08:00

README.md

DC3 API Data

dc3-api-data defines gRPC contracts for values, commands, events, status, and system-health queries. Generated Java types use io.github.pnoker.api.center.data; proto sources live under src/main/protobuf/api/common/data/.

Services

Service	RPCs	Purpose
`PointValueApi`	`GetLastValue`, `ListHistoryValues`, `ListSeriesVolumes`	query point values and value-volume series
`PointValueApi`	`ReadCommand`, `WriteCommand`	submit point read/write commands
`CommandHistoryApi`	`CallCommand`, `GetByRecordId`, `ListByPage`	dispatch and query command history
`EventHistoryApi`	`ReportEvent`, `GetByRecordId`, `ListByPage`	report and query event history
`StatusHealthApi`	`DeviceStatusesByIds`, `DeviceStatusesByProfileId`	query device status snapshots
`StatusHealthApi`	`DriverStatusesByIds`, `DriverDeviceStatusSummary`	query driver status snapshots and device summaries
`StatusHealthApi`	`SystemHealth`	query the platform health snapshot

Single-result RPCs use GetXxx; collection/page results use ListXxx or an explicitly named status aggregation. Do not reintroduce legacy SelectXxx names.

Consumers and implementation

dc3-common-data implements the data-side servers.
dc3-common-facade-grpc wraps generated stubs in transport-independent facades.
Manager and other business modules should call the facade API rather than construct channels directly.

All write/report requests must carry tenant context through the transport and into the business layer.

Build and Verification

mvn -s .mvn/settings.xml -q -pl dc3-api/dc3-api-data -am compile

This contract module has no module-specific tests. Compile it after proto changes, then run the matching server and facade tests in dc3-common-data and dc3-common-facade-grpc.