View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000271310000-005: Information Modelpublic2014-02-03 17:552022-08-02 16:30
ReporterJouni Aro Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionwon't fix 
Product Version1.02 
Summary0002713: OperationLimits: MaxNodesPerHistoryUpdateData vs. MaxNodesPerHistoryUpdateEvents
Description

While thinking about an implementation for these limits, I was left wondering, why do we have these limits separately. The historyUpdate call has a parameter HistoryUpdateDetails, which can contain both data and event updates, so it would only make sense to define a MaxNodesPerHistoryUpdate.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0008176 closedJim Luth Operation limit client usage for MaxNodesPerHistoryUpdateData/Events is unclear with description in the spec 

Activities

Jim Luth

2014-03-04 18:57

administrator   ~0005304

These limits are suggestions by the server and the practical limit may be less in a particular instance. If the caller wants to be sure the limits will apply then the caller should not mix Data and Event updates in a single call.

Jim Luth

2014-03-04 18:57

administrator   ~0005305

see previous note

Issue History

Date Modified Username Field Change
2014-02-03 17:55 Jouni Aro New Issue
2014-03-04 18:57 Jim Luth Note Added: 0005304
2014-03-04 18:57 Jim Luth Status new => closed
2014-03-04 18:57 Jim Luth Note Added: 0005305
2014-03-04 18:57 Jim Luth Resolution open => won't fix
2022-08-02 16:30 Jim Luth Relationship added related to 0008176