Necessary Table

7/30/2019 Necessary Table

1/9

The following table describes the seven possible types of

synchronisation as presented in

OMA DS specifications:

mode Sync Scenario Description

200 Two-way synchronisation

(Rapid

Sync)

A normal synchronisation

type in which the

client and the server

exchange information

about modified data inthese devices. The

client sends the

modifications first.

201 Slow synchronisation (Slow

Sync)

A form of two-way

synchronisation in which

all records are compared

with each other on a

field-by-field basis. Inpractice, this means

that the client sends all its

data from a

database to the server and

the server does the

synchronisation analysis

(field-by-field) for

this data and the data in

the server.

202 One-way synchronisation

from

client only (Rapid Export)

A synchronisation type in

which the client

sends its modifications to

the server but the


2/9

server does not send its

modifications back to

the client.

203 Refresh synchronisation

from clientonly (Slow Export)


which the clientsends all its data from a

database to the server

(i.e., exports). The server

is expected to

replace all data in the

target database with the

data sent by the client.

Server does thesynchronisation analysis

just like the Slow

synchronisation scenario

and determines

which information is

kept, based on the

conflict resolution to

apply. In practice,Refresh synchronisation

from client is like a

Slow synchronisation

without modification on

client.

204 One-way synchronisation

from

server only (Rapid Import)


which the client

gets all modifications

from the server but theclient does not send its

modifications to the

server.


3/9

205 Refresh synchronisation

from server

only (Slow Import)


which the server

sends all its data from a

database to the client.

The client is expected toreplace all data in the

target database with the

data sent by the

server. In practice,

Refresh synchronisation

from server is like a Slow

synchronisation

without modification onserver. Replacement

process may differ on

different manufacturer

solutions.

206 Server Alerted

synchronisation.

A sync type in which the

server alerts the

client to perform

synchronisation. See[SAN]

TAGS:- SupportLargObjs [DEVINF]

- MaxObjSize [META]- MaxMsgSize [META]

- Size [META]- MoreData [REPPRO][DSREPU]

STATUS CODES AND ALERTS:


4/9

STATUS CODES DESCRIPTION213 Chunked item accepted and

buffered [REPPRO]222 NEXT MESSAGE [DSPROTO]

[DSREPU]

223 End of Data for chunked objectnot received [SYNCPRO][DSREPU]

424 Size Mismatch [REPPRO]

416 Request entity too large[REPPRO]

411 Size REQUIRED. The requestedcommand MUST be accompanied

by byte size or

length information in the Meta

element type [REPPRO]


5/9

The following table summarizes the different Status andAlert codes that the server can potentially use in itsanswer to a Resume request sent by the client, as well as

the expected client behaviour:

Status code Alert code Meaning Client behaviour200 Same Sync type

codeas in the previousinterruptedsession

The resumptionof thesession isaccepted by bothclient and server

The client MUSTresume theinterrupted session.

200 Sync type code

differentfrom the previousinterruptedsession one

NOT POSSIBLE

The server isnot OMA DS1.2 compliant inthat case

The client MUST end

theresumed session infailure witha relevant error statuscode

508 Slow Sync typecode 201

The serverrefuses toresumethe session andforces a Slow

Sync.

The client MUSTperform aSlow Sync

508 Sync type code205

The serverrefuses toresumethe session andindicates the newSync type itwants touse.

In an enterpriseenvironment,there aretimes when theserverwould prefer aRefresh

The client MAY accepttheoverride or end theresumed session infailure with arelevant error statuscode


6/9

from Server

type of Sync(Alert 205)rather than a

fullSlow Sync(Alert 201). Theuse case forthis is whenthe clientdevice type isknown tocorrupt data(eg.

May use vcalonly and mayintroduceoddities inrepresentationofexceptions torecurringevents which

MUST NOT bepropagated tothe serverdatastore.)


7/9

Alert Codes

Here are listed all Alert codes and values, which are used in the Data

element when the Alert command is sent.

Alert Codes used for user alerts

Alert Code Value Name Description100 DISPLAY Show. The Data element type

contains contentinformation that should beprocessed and displayedthrough the user agent.

101-150 - Reserved for future SyncMLusage.

Alert Codes used at the synchronization initialization

Alert CodeValue

Name Description

200 TWO-WAY Specifies a client-initiated, twoway sync.

201 SLOW SYNC Specifies a client-initiated, twoway slow-sync.

202 ONE-WAY FROMCLIENT

Specifies the client-initiated,one-way only sync from theclient to the server.

203 REFRESH FROMCLIENT

Specifies the client-initiated,refresh operation for the

onewayonly sync from the client to theserver.

204 ONE-WAY FROMSERVER

Specifies the client-initiated,one-way only sync from theserver to the client.

205 REFRESH FROM Specifies the client-initiated,


8/9

SERVER refresh operation of theonewayonly sync from the server tothe client.

Alert Codes used by the server when alerting the

sync.

Alert Code

Value

Name Description

206 TWO-WAY BY SERVER Specifies a server-initiated,two-way sync.

207 ONE-WAY FROMCLIENT BY SERVER

Specifies the server-initiated, one-way only syncfrom theclient to the server.

208 REFRESH FROMCLIENT BY SERVER

Specifies the server-initiated, refresh operation

for theone-way only sync from theclient to the server.

209 ONE-WAY FROMSERVER BY SERVER

Specifies the server-initiated, one-way only syncfrom theserver to the client.

210 REFRESH FROMSERVER BY SERVER

Specifies the server-initiated, refresh operation ofthe onewayonly sync from the server tothe client.

211-220 - Reserved for future SyncMLusage.


9/9

Special Alert Codes

Alert Code Value Name Description221 RESULT ALERT Specifies a request for sync

results.222 NEXT MESSAGE Specifies a request for the next

message in the package.

223 NO END OF DATA End of Data for chunked object noreceived.

224 SUSPEND Suspend Synchronization session

225 RESUME Resume Synchronization session226 DATA MANAGEMENT Specifies a request for data

management without

synchronization.227-250 - Reserved for future SyncMLusage.

Necessary Table

Documents

Transcript of Necessary Table