vervis/migrations/2019_03_19.model

RemoteRawObject
    content  PersistJSONObject
    received UTCTime

RemoteDiscussion
    sharer        RemoteSharerId
    instance      InstanceId
    ident         Text
    discuss       DiscussionId

    UniqueRemoteDiscussionIdent instance ident
    UniqueRemoteDiscussion discuss

LocalMessage
    author         PersonId
    rest           MessageId

    UniqueLocalMessage rest

RemoteMessage
    author     RemoteSharerId
    instance   InstanceId
    ident      Text
    rest       MessageId
    raw        RemoteRawObjectId
    lostParent Text              Maybe

    UniqueRemoteMessageIdent instance ident
    UniqueRemoteMessage rest
Add route getMessageR, returns an Activity Note for any locally created Message 2019-03-23 05:46:42 +09:00			`RemoteRawObject`
Switch OutboxItem's Activity from plain BL to an upgraded PersistJSONObject 2019-06-29 12:19:00 +09:00			`content PersistJSONObject`
Receive remote comments on local ticket discussion 2019-03-22 07:57:15 +09:00			`received UTCTime`

Add route getMessageR, returns an Activity Note for any locally created Message 2019-03-23 05:46:42 +09:00			`RemoteDiscussion`
Make the DB migrations not depend on current model 2019-04-11 22:26:57 +09:00			`sharer RemoteSharerId`
Create Note outbox handler, not in use yet I wrote a function handleOutboxNote that's supposed to do the whole outbox POST handler process. There's an outbox item table in the DB now, I adapted things in various source files. Ticket comment federation work is still in progress. 2019-03-29 06:08:30 +09:00			`instance InstanceId`
			`ident Text`
			`discuss DiscussionId`
Add route getMessageR, returns an Activity Note for any locally created Message 2019-03-23 05:46:42 +09:00
			`UniqueRemoteDiscussionIdent instance ident`
			`UniqueRemoteDiscussion discuss`

In ticket comment tree, support mixing local and remote (federated) comments 2019-03-20 17:07:37 +09:00			`LocalMessage`
Create Note outbox handler, not in use yet I wrote a function handleOutboxNote that's supposed to do the whole outbox POST handler process. There's an outbox item table in the DB now, I adapted things in various source files. Ticket comment federation work is still in progress. 2019-03-29 06:08:30 +09:00			`author PersonId`
			`rest MessageId`
In ticket comment tree, support mixing local and remote (federated) comments 2019-03-20 17:07:37 +09:00
			`UniqueLocalMessage rest`

			`RemoteMessage`
Receive remote comments on local ticket discussion 2019-03-22 07:57:15 +09:00			`author RemoteSharerId`
			`instance InstanceId`
			`ident Text`
			`rest MessageId`
Add route getMessageR, returns an Activity Note for any locally created Message 2019-03-23 05:46:42 +09:00			`raw RemoteRawObjectId`
			`lostParent Text Maybe`
In ticket comment tree, support mixing local and remote (federated) comments 2019-03-20 17:07:37 +09:00
Receive remote comments on local ticket discussion 2019-03-22 07:57:15 +09:00			`UniqueRemoteMessageIdent instance ident`
In ticket comment tree, support mixing local and remote (federated) comments 2019-03-20 17:07:37 +09:00			`UniqueRemoteMessage rest`