Hi Tim,
thank you for your quick response. As of now, I really can not use the
restlet framework at all. During the login I have 3 calls,
all of them taking in sum so much time, that in 80% the thread call times
out…
I may have another solution, which might work for our case.
Because we wrote our server ourself, I definitely know that we do not use
header data at all, especially we do not use
any dates like Expires, etc.
So it might be a solution to introduce a generic switch, which disable the
header processing in total.
Here some pseudo code, to get an Idea:
Engine.getInstance().getGlobalPreferences().set(Client.FEATURE_DISABLE_HEADER_PROCESSING,
true);
//in ClientAdapter.toSpecific()
if
((Boolean)context.getPreferences(Client.FEATURE_DISABLE_HEADER_PROCESSING)){
HeaderUtils.addGeneralHeaders();
}
What do you think about my idea? If you see the RestEasy framework, you can
see such an FEATURE approach,
to configure the internal processing.
As for now, I must switch back to the simple HTTP4 Client solution :(
Cheers
Fritz
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/Reading-setting-date-header-fields-is-extreme-slow-on-android-tp6033977p6035082.html
Sent from the Restlet Discuss mailing list archive at Nabble.com.
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2704963
