Problems with signature in MS Azure IIS

Hi.
We have now started to deploy our application in the cloud via Microsoft Azure and the signature is causing us problems.
In the forms OnCreate handler we have the following:
var
JS: string;
bparam: TIWCGBrowserParam;
begin
LDataType:= TIWCGJQSignatureDataType(SigDataTypeNumber);
JS:=Signaturen.JQSignatureOptions.jsGetData(LDataType, False);
BtnSignera.JQMButtonOptions.Events.OnVClick.BrowserParams.Clear;
bparam:=BtnSignera.JQMButtonOptions.Events.OnVClick.BrowserParams.Add;
bparam.ServerName:= 'sigdata';
bparam.BrowserScript:= JS;
end;
In our stand alone environments it works as expected but the cloud seems to impose a limitation to the size of the "sigdata" param for the request. According to our cloud guy the signature is causing the URL to exceed the size limitation and breaks the functionality.
Is there a way around this?
T.I.A.
Sören Alexandersson
We have now started to deploy our application in the cloud via Microsoft Azure and the signature is causing us problems.
In the forms OnCreate handler we have the following:
var
JS: string;
bparam: TIWCGBrowserParam;
begin
LDataType:= TIWCGJQSignatureDataType(SigDataTypeNumber);
JS:=Signaturen.JQSignatureOptions.jsGetData(LDataType, False);
BtnSignera.JQMButtonOptions.Events.OnVClick.BrowserParams.Clear;
bparam:=BtnSignera.JQMButtonOptions.Events.OnVClick.BrowserParams.Add;
bparam.ServerName:= 'sigdata';
bparam.BrowserScript:= JS;
end;
In our stand alone environments it works as expected but the cloud seems to impose a limitation to the size of the "sigdata" param for the request. According to our cloud guy the signature is causing the URL to exceed the size limitation and breaks the functionality.
Is there a way around this?
T.I.A.
Sören Alexandersson