Repository navigation
TACTIC compatibility
Compatibility is behavioral: original scripts, configurations, plugins and SDK calls must preserve their supported meaning. A method name, class registration or successful modern-client screen is not proof of complete legacy compatibility. Use live API discovery for the selected installation and check actual arguments, results, authorization, revisions, transaction effects and failure paths.
Handler activity requests bind their RPC context to the selected project, falling
back to sthpw only without a project. Original Schema.get_foreign_keys strips
project qualifiers and inspects column metadata in the active request database;
selecting schema XML alone is insufficient. Journal Search Types retain explicit
sthpw/... qualification. Browser Activity Feed already runs in its request
project. The XML-RPC regression invokes the actual Handler client with legacy
metadata behavior and checks linked titles, keys and the database context.
Handler's maintained Stream-boundary inventory lives in its
docs/tactic_compatibility/stream_api.md and stream_boundaries.json.
The desktop client enables extensions only for a confirmed server/login/ticket;
Legacy and unknown sessions keep native search, check-in, hooks and HTML/Mako
layouts. Stream table management, typed item metadata, private file transfers,
configured page resolution and server check-in queue requests are gated at their
owners, including deferred work. Shared menus hide the Stream manager while
retaining native view actions. Remote check-in references remain stored and are
never replayed through legacy check-in after a session change.
tests/test_legacy_stream_boundaries.py runs both native and transported Handler
sources without the Stream namespace: simple nested filter expressions retain
native evaluation and parent scope, HTML layouts work, and typed Stream layouts
return an explicit marker before imports. Installed Stream dependency failures
remain errors; Stream access callbacks and expression write denial stay active.
PluginManagerCmd is a Stream extension even though original TACTIC has plugin
installation commands and widgets. Handler hides the Stream manager for Legacy
and unidentified API sessions, blocking uploads and queued command execution
before server contact. Shared administration navigation applies this same
filter; Stream keeps the manager and legacy plugins remain usable independently.
DashboardCmd and Stream widget-configuration authoring are Stream extensions. Handler hides page/item layout editors for Legacy and unidentified API sessions; native and browser administration descriptions use the same section filtering. Browser Stream sessions retain both editors. Controller guards cover direct, queued and preview requests, including a change away from a Stream session.
Transported Handler procedures use public pyasm.common exception exports.
Legacy TACTIC re-exports SecurityException from common_exception.py and lacks
Stream's pyasm.common.errors module. Physical-table tests execute both products'
procedure sources without that import and verify administrator enforcement;
the native Python procedure transport also exercises the actual Handler source.
Legacy Sql.clear_results() replaces rows in its previous result list with
None before each query. Raw PostgreSQL metadata must be consumed before the
primary-key query. Both procedure sources follow this ordering; the regression
executes the original legacy clearing method and checks empty tables, NULL
defaults and NULL cells alongside the normal SQL-backed CRUD/rollback tests.
Handler security-group catalog procedures and Stream's native counterpart use
the legacy Search.add_column signature. Fixed aggregate expressions such as
MAX(id) use Search.get_select().set_quoted_mode('none') instead of a quoted
keyword. SQL-backed tests check both implementations with the old signature and
compare grouped journal markers with each group's latest revision; administrator
checks, stale-write protection and safe user projections remain required.
| Boundary | Reference |
|---|---|
| Supported and excluded server contracts | API compatibility Help |
| Native object/query semantics | Core model |
| Original project page URLs | Custom URL contract and limits |
| Original table configurations | Table contract, widget catalogue |
| TS APIs and original server references | Source index |
| TH client interpretation of TACTIC | Handler compatibility map |
Use the unchanged client/script against disposable data. Compare stored values and side effects, not only presentation. Check both SQLite and PostgreSQL when a database contract changes; inspect TH and TS separately for shared UI workflows. Existing test and tool sources are the reproducible evidence owners. Record package/source fingerprints and the precise tested scope with each new run.
The excluded old pyasm.prod subsystem is distinct from ordinary configurable
VFX projects. Maya/applets are excluded from the current acceptance scope.
Unsupported behavior must be reported explicitly. Historical migration audits
are retained in the local workspace archive; their counts are not current status.
TACTIC-Stream · Releases · Issues · English · Русский
English
- Home
- Installation
- Feature tour
- User guide
- Assistant
- Dashboards
- Knowledge Base
- Synology DSM
- Demo projects
Русский
- Главная
- Установка
- Обзор возможностей
- Руководство пользователя
- Помощник
- Дашборды
- База знаний
- Synology DSM
- Демо-проекты
Development / Разработка