dcesrv_fault and custom pfc_flags

[Julien Kerihuel]

Hi List,

dcesrv_fault (source/rpc_server/dcerpc_server.c:456) statically defines
pfc_flags to DCERPC_PFC_FLAG_FIRST | DCERPC_PFC_FLAG_LAST.

Outlook is perfectly happy with this, so it's not a real issue. In the
meantime, Exchange also sets the DCERPC_PFC_FLAG_DID_NOT_EXECUTE flag
(depending on the context). 

Would it make sense to add a field to the dcesrv_call_state structure
and let developers control the pfc_flags value? 

If the value is unset in developer's code, then fall back to the default
existing value. This way, this shouldn't impact on existing code.

Cheers,
Julien.

-- 
Julien Kerihuel
j.kerihuel at openchange.org
OpenChange Project Manager

GPG Fingerprint: 0B55 783D A781 6329 108A  B609 7EF6 FE11 A35F 1F79

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/samba-technical/attachments/20080513/a0519857/attachment.bin