• last updated 14 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
- if one is handling ::db::Object slots generally, to it correctly (including "object_id")

- reduce redundancy

Backport changes from downstream: add CrItems we skip as they are handled by ::xo::db::Object already

add test cases from the xotcl-core DB tutorial

    • -0
    • +261
    ./test/xotcl-core-db-tutorial-procs.tcl
file xotcl-core-db-tutorial-procs.tcl was initially added on branch oacs-5-10.

    • -0
    • +0
    ./test/xotcl-core-db-tutorial-procs.tcl
Improve boolean existance checks

Add a couple more tests about properties of revisions

Add basic CrItem tests

Basic tests of ::xo::db::Object and ::xo::db::Class

file xotcl-test-procs.tcl was initially added on branch oacs-5-10.

    • -0
    • +0
    ./test/xotcl-test-procs.tcl
Replace legacy acs_permission__permission_p with acs_permission.permission_p

  1. … 2 more files in changeset.
Make sure a context_id is there

improve spelling

  1. … 4 more files in changeset.
improve spelling

  1. … 9 more files in changeset.
improve spelling

  1. … 7 more files in changeset.
Fix typo

Allow allow to specify context_id for the object in save and save_new methods

Add acs_object attributes to ::xo::db::Object slots definition

Pretty names have been taken from acs_attributes defined on a vanilla instance on acs_object, which apparently are not localized. Changes to cr-procs are to make sure new object members from slots don't interfere with previous behavior for CrItems

Don't call security::secure_conn_p if not connected

message-relay-procs: factor out subscription handling from bgdelivery

and chat-procs and provide compatibility for streaming chat modes

with HTTPS.

The message-relay-procs provide two different implementation for

delivering messages to subscribers:

a) via bgdelivery (traditional method): this is, what was used so far,

having the disadvantage that it only works on plain HTTP connections

b) via ns_connchan (new method): ns_connchan is a relatively new feature

of NaviServer which allows transparent reading/writing from connections.

Chat has a new instance variable named "message_relay", which consists

of preferences for the chat connections. So far, the traditional "bgdelivery"

is still the default mode.

bumped version numbers

- xotcl-core 5.10.0d14

- xowiki: 5.10.0d23

  1. … 4 more files in changeset.
file message-relay-procs.tcl was initially added on branch oacs-5-10.

    • -0
    • +0
    ./message-relay-procs.tcl
reduce verbosity

report server tag name as well to get precise version info

Remove unwanted change

Reflect changes in util__table_column_exists in tcl api and make xotcl-core dependant on latest acs-kernel

  1. … 1 more file in changeset.
xo::broadcast: allow to send messages to threads seleced via pattern

address global variable __csrf_token directly

  1. … 1 more file in changeset.
Use the database to check whether default table values looking different actually are once casted to the column datatype

handle different variants of boolean return values from the DB

improve comments

add thread object name for naming mutex and make creation/destroy logging more conformant