1460888873-5a86add1-12fb-4ce1-93da-b0f72123bdd7

1. A parking brake device for a vehicle having a plurality of wheels, having at least one freewheel lock, the freewheel lock comprising:
an inner ring, and
an outer ring,
wherein the inner ring and the outer ring have faces which are situated so as to face toward one another and are formed as opposing cone faces forming an annular gap,
wherein a plurality of brake bodies designed as conical rollers are arranged between said faces,
wherein the conical rollers are movable by associated actuating members into a release position and into a braking position, and
wherein a cone angle of each conical roller is smaller by a defined magnitude than a limit angle arising from a value of the tangent taking into consideration friction angles between the conical rollers and the cone faces of the inner ring and the outer ring.
2. The parking brake device as claimed in claim 1, wherein the conical rollers can be moved in their longitudinal direction, and wherein the inner ring and the outer ring are prevented from being displaced axially.
3. The parking brake device as claimed in claim 2, wherein each conical roller can be moved into the braking position by at least one pressure spring.
4. The parking brake device as claimed in claim 1, wherein each actuating member is a pneumatically operating actuating member.
5. The parking brake device as claimed in claim 1, wherein at least one of the inner and outer rings has clamping ramps for the conical rollers.
6. The parking brake device as claimed in claim 5, wherein the clamping ramps are designed so as to be single-acting or double-acting.
7. The parking brake device as claimed in claim 1, further comprising a substantially closed housing in which the parking brake device is arranged.
8. The parking brake device as claimed in claim 5, wherein the at least one ring is the outer ring.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

We claim:

1. A method for selectively handling data processing requests in a computer communications network comprising the steps of:
identifying at least one type of dynamic data processing which can be performed in an edge server;
detecting a request for dynamic data processing in network distributable markup;
determining whether said edge server can perform said requested dynamic data processing based upon said identified types of dynamic data processing which can be performed in said edge server; and,
deferring processing of said request to an edge server if it is determined that said edge server can perform said requested dynamic data processing.
2. The method of claim 1, wherein said deferring step comprises the steps of:
determining whether it is preferable to defer processing of said request to an edge server; and,
deferring processing of said request to an edge server if it is determined that it is preferable to defer processing of said request to said edge server.
3. The method of claim 1, further comprising the steps of:
if it is determined that said dynamic data processing can be performed in said edge server, generating markup which contains said request for dynamic data processing, encapsulating said markup in a response, and, forwarding said response to said edge server, wherein said edge server can perform said deferred processing.
4. The method of claim 3, further comprising the steps of:
if it is determined that said dynamic data processing cannot be performed in said edge server, performing said data processing, said data processing producing a result, generating markup which contains said result, encapsulating said markup in a response, and, forwarding said response to said edge server, wherein said edge server can forward said response to requesting user.
5. A method for selectively handling data processing requests in a computer communications network comprising the steps of:
configuring a tag handler to perform dynamic data processing;
further configuring said tag handler to identify whether a specified edge server can perform said dynamic data processing;
establishing a tag definition corresponding to said tag handler; and,
embedding references to said tag definition and said tag handler in network distributable markup,
whereby an origin server processing said markup can locate said tag handler based upon said tag definition and can determine from said tag handler whether to defer processing of a data processing request to said specified edge server or whether to process said request locally in said origin server.
6. A system for selectively processing a request for dynamic data processing in a computer communications network comprising:
a tag handler library comprising a plurality of tag handlers configured to perform dynamic data processing;
a tag definition file comprising a plurality of tag definitions, each said tag definition associating a tag handler with a particular markup language tag;
an application processor configured to process markup and to invoke tag handlers corresponding to particular markup language tags detected in said markup as specified by tag definitions in said tag definition file; and,
deferred processing logic configured to modify a request header to specify which types of dynamic data processing said system can process, said deferred processing logic being further configured to pre-process markup for processing in said application processor.
7. The system of claim 6, wherein said tag handler comprises a Java class.
8. The system of claim 6, wherein said markup is a Java Server Page (JSP) and said markup language tag is a customized JSP tag.
9. A method for selectively handling data processing requests in a computer communications network comprising the steps of:
receiving in an edge server an HTTP request for a Java Server Page (JSP), said HTTP request comprising an HTTP request header;
modifying said HTTP request header to indicate whether said edge server can process JSP program fragments having particular markup tags;
forwarding said HTTP request comprising said modified HTTP request header to an origin server, said origin server processing said HTTP request by serving said requested JSP, but deferring processing of any JSP program fragments in said JSP having said particular markup tags, and returning said requested JSP to said edge server; and,
processing said deferred JSP program fragments in said edge server.
10. The method of claim 9, wherein said modifying step comprises:
determining whether said edge server is configured to process JSP program fragments having particular markup tags;
if it is determined that said edge server is not configured to process JSP program fragments having particular markup tags, configuring said edge server with selected markup tag handlers so that said edge server can process said JSP program fragments; and,
modifying said HTTP request header to indicate that said edge server can process said JSP program fragments having said particular markup tags;
11. A machine readable storage having stored thereon a computer program for selectively handling data processing requests in a computer communications network, said computer program having a plurality of code sections executable by a machine for causing the machine to perform the steps of:
identifying at least one type of dynamic data processing which can be performed in an edge server;
detecting a request for dynamic data processing in network distributable markup;
determining whether said edge server can perform said requested dynamic data processing based upon said identified types of dynamic data processing which can be performed in said edge server; and,
deferring processing of said request to an edge server if it is determined that said edge server can perform said requested dynamic data processing.
12. The machine readable storage of claim 11, wherein said deferring step comprises the steps of:
determining whether it is preferable to defer processing of said request to an edge server; and,
deferring processing of said request to an edge server if it is determined that it is preferable to defer processing of said request to said edge server.
13. The machine readable storage of claim 11, further comprising the steps of:
if it is determined that said dynamic data processing can be performed in said edge server, generating markup which contains said request for dynamic data processing, encapsulating said markup in a response, and, forwarding said response to said edge server, wherein said edge server can perform said deferred processing.
14. The machine readable storage of claim 13, further comprising the steps of:
if it is determined that said dynamic data processing cannot be performed in said edge server, performing said data processing, said data processing producing a result, generating markup which contains said result, encapsulating said markup in a response, and, forwarding said response to said edge server, wherein said edge server can forward said response to requesting user.
15. A machine readable storage storing thereon a computer program for selectively handling data processing requests in a computer communications network, said computer program having a plurality of code sections executable by a machine for causing the machine to perform the steps of:
receiving in an edge server an HTTP request for a Java Server Page (JSP), said HTTP request comprising an HTTP request header;
modifying said HTTP request header to indicate whether said edge server can process JSP program fragments having particular markup tags;
forwarding said HTTP request comprising said modified HTTP request header to an origin server, said origin server processing said HTTP request by serving said requested JSP, but deferring processing of any JSP program fragments in said JSP having said particular markup tags, and returning said requested JSP to said edge server; and,
processing said deferred JSP program fragments in said edge server.
16. The machine readable storage of claim 15, wherein said modifying step comprises:
determining whether said edge server is configured to process JSP program fragments having particular markup tags;
if it is determined that said edge server is not configured to process JSP program fragments having particular markup tags, configuring said edge server with selected markup tag handlers so that said edge server can process said JSP program fragments; and,
modifying said HTTP request header to indicate that said edge server can process said JSP program fragments having said particular markup tags;