1460779650-74548e65-b0fa-4f13-99a8-e4f78f1663dc

1. A method for performing a transaction, comprising:
(a) receiving an initiate-application command from a user at an application server;
(b) in response to receiving the initiate-application command, initiating an application associated with the initiate-application command, wherein the application facilitates a transaction;
(c) presenting in a single web page a parameter-request panel to the user at a client, wherein the parameter-request panel includes a set of parameter-request fields;
(d) receiving from the user transaction parameters contained in the parameter-request fields of the parameter-request panel;
(e) in response to receiving the transaction parameters, presenting in the single web page a transaction-options panel to the user without obscuring the parameter-request panel, wherein the transaction-options panel includes a set of transaction options associated with the transaction parameters;
(f) receiving from the user a transaction option selection associated with the set of transaction options;
(g) in response to receiving the transaction-option selection, presenting in the single web page a transaction-completion panel to the user without obscuring the parameter-request panel and the transaction-options panel, wherein the transaction-completion panel includes a set of transaction-completion fields associated with the transaction-option selection;
(h) receiving from the user transaction-completion information contained in the transaction-completion fields of the transaction-completion panel; and
(i) in response to receiving the transaction-completion information, completing the transaction.
2. The method of claim 1, wherein initiating the application involves:
(a) initiating an application back-end at the application server, wherein the application back-end performs server-side processing associated with the application;
(b) downloading to the client an application front-end, wherein the application front-end performs client-side processing associated with the application; and
(c) initiating the application front-end at the client.
3. The method of claim 2, wherein initiating the application front-end involves:
(a) loading the parameter-request panel into the single web page, wherein the parameter-request panel is active;
(b) loading the transaction-options panel into the single web page, wherein the transaction-options panel is inactive;
(c) loading the set of parameter-request fields into the parameter-request panel; and
(d) presenting the single web page to the user at the client.
4. The method of claim 1, wherein the transaction can include:
(a) a product transaction, which involves purchasing a product;
(b) a service transaction, which involves purchasing a service;
(c) a configuration transaction, which involves configuring the application; and
(d) an information transaction, which involves presenting information to the user.
5. The method of claim 1, wherein presenting the transaction-options panel to the user involves:
(a) loading the set of transaction options into the transaction-options panel;
(b) loading data associated with each transaction option from the set of transaction options into the transaction-options panel; and
(c) making the transaction-options panel active without modifying the parameter-request panel.
6. The method of claim 1, wherein, in response to receiving the transaction-option selection, the method further comprises replacing the set of transaction options included in the transaction-options panel with detail information associated with the transaction-option selection.
7. The method of claim 6, wherein, after receiving the transaction-option selection, the method further comprises:
(a) receiving a request to review the set of transaction options; and
(b) in response to receiving the request to review the set of transactions options,
(i) hiding the transaction-completion panel,
(ii) restoring the transaction-options panel to its original size, and
(iii) replacing the detail information associated with the transaction-option selection with the set of transaction options.
8. The method of claim 6, wherein, after receiving the transaction-completion information, the method further comprises updating the detail information to include information associated with the transaction-completion information.
9. The method of claim 1, wherein presenting the transaction-completion panel to the user involves:
(a) reducing the size of the transaction-options panel from its original size to a reduced size;
(b) loading the transaction-completion panel into the single web page; and
(c) making the transaction-completion panel active without modifying the parameter-request panel and without making additional modifications to the transaction-options panel.
10. The method of claim 1, wherein completing the transaction involves:
(a) finalizing the transaction;
(b) creating confirmation documents; and
(c) sending the confirmation documents to the user.
11. The method of claim 1, wherein the method further comprises:
(a) receiving new transaction parameters from the user; and
(b) in response to receiving the new transaction parameters,
(i) modifying the set of transaction options to include a new set of transaction options associated with the new transaction parameters, and
(ii) modifying the set of transaction-completion fields to include a new set of transaction-completion fields associated with the new set of transaction options.
12. A non-transitory computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for performing a transaction, the method comprising:
(a) receiving an initiate-application command from a user at an application server;
(b) in response to receiving the initiate-application command, initiating an application associated with the initiate-application command, wherein the application facilitates a transaction;
(c) presenting in a single web page a parameter-request panel to the user at a client, wherein the parameter-request panel includes a set of parameter-request fields;
(d) receiving from the user transaction parameters contained in the parameter-request fields of the parameter-request panel;
(e) in response to receiving the transaction parameters, presenting in the single web page a transaction-options panel to the user without obscuring the parameter-request panel, wherein the transaction-options panel includes a set of transaction options associated with the transaction parameters;
(f) receiving from the user a transaction-option selection associated with the set of transaction options;
(g) in response to receiving the transaction-option selection, presenting in the single web page a transaction-completion panel to the user without obscuring the parameter-request panel and the transaction-options panel, wherein the transaction-completion panel includes a set of transaction-completion fields associated with the transaction-option selection;
(h) receiving from the user transaction-completion information contained in the transaction-completion fields of the transaction-completion panel; and
(i) in response to receiving the transaction-completion information, completing the transaction.
13. The non-transitory computer-readable storage medium of claim 12, wherein initiating the application involves:
(a) initiating an application back-end at the application server, wherein the application back-end performs server-side processing associated with the application;
(b) downloading to the client an application front-end, wherein the application front-end performs client-side processing associated with the application; and
(c) initiating the application front-end at the client.
14. The non-transitory computer-readable storage medium of claim 13, wherein initiating the application front-end involves:
(a) loading the parameter-request panel into the single web page, wherein the parameter-request panel is active;
(b) loading the transaction-options panel into the single web page, wherein the transaction-options panel is inactive;
(b) loading the set of parameter-request fields into the parameter-request panel; and
(c) presenting the single web page to the user at the client.
15. The non-transitory computer-readable storage medium of claim 12, wherein the transaction can include:
(a) a product transaction, which involves purchasing a product;
(b) a service transaction, which involves purchasing a service;
(c) a configuration transaction, which involves configuring the application; and
(d) an information transaction, which involves presenting information to the user.
16. The non-transitory computer-readable storage medium of claim 12, wherein presenting the transaction-options panel to the user involves:
(a) loading the set of transaction options into the transaction-options panel;
(b) loading data associated with each transaction option from the set of transaction options into the transaction-options panel; and
(c) making the transaction-options panel active without modifying the parameter-request panel.
17. The non-transitory computer-readable storage medium of claim 12, wherein, in response to receiving the transaction-option selection, the method further comprises replacing the set of transaction options included in the transaction-options panel with detail information associated with the transaction-option selection.
18. The non-transitory computer-readable storage medium of claim 17, wherein, after receiving the transaction-option selection, the method further comprises:
(a) receiving a request to review the set of transaction options; and
(b) in response to receiving the request to review the set of transactions options,
(i) hiding the transaction-completion panel,
(ii) restoring the transaction-options panel to its original size, and
(iii) replacing the detail information associated with the transaction-option selection with the set of transaction options.
19. The non-transitory computer-readable storage medium of claim 17, wherein, after receiving the transaction-completion information, the method further comprises updating the detail information to include information associated with the transaction-completion information.
20. The non-transitory computer-readable storage medium of claim 12, wherein presenting the transaction-completion panel to the user involves:
(a) reducing the size of the transaction-options panel from its original size to a reduced size;
(b) loading the transaction-completion panel into the single web page; and
(c) making the transaction-completion panel active without modifying the parameter-request panel and without making additional modifications to the transaction-options panel.
21. The non-transitory computer-readable storage medium of claim 12, wherein completing the transaction involves:
(a) finalizing the transaction;
(b) creating confirmation documents; and
(c) sending the confirmation documents to the user.
22. The non-transitory computer-readable storage medium of claim 12, wherein the method further comprises:
(a) receiving new transaction parameters from the user; and
(b) in response to receiving the new transaction parameters,
(i) modifying the set of transaction options to include a new set of transaction options associated with the new transaction parameters, and
(ii) modifying the set of transaction-completion fields to include a new set of transaction-completion fields associated with the new set of transaction options.
23. An apparatus that performs a transaction, comprising:
(a) a receiving mechanism configured to receive an initiate-application command from a user at an application server;
(b) an initiation mechanism configured to initiate an application associated with the initiate-application command, wherein the application facilitates a transaction;
(c) a presentation mechanism configured to present in a single web page a parameter-request panel to the user at a client, wherein the parameter-request panel includes a set of parameter-request fields;
(d) the receiving mechanism further configured to receive from the user transaction parameters contained in the parameter-request fields of the parameter-request panel;
(e) the presentation mechanism further configured to present in the single web page a transaction-options panel to the user without obscuring the parameter-request panel, wherein the transaction-options panel includes a set of transaction options associated with the transaction parameters;
(f) the receiving mechanism further configured to receive from the user a transaction-option selection associated with the set of transaction options;
(g) the presentation mechanism further configured to present in the single web page a transaction-completion panel to the user without obscuring the parameter-request panel and the transaction-options panel, wherein the transaction-completion panel includes a set of transaction-completion fields associated with the transaction-option selection;
(h) the receiving mechanism further configured to receive from the user transaction-completion information contained in the transaction-completion fields of the transaction-completion panel; and
(i) a completion mechanism configured to complete the transaction.
24. The apparatus of claim 23, wherein the initiation mechanism is further configured to:
(a) initiate an application back-end at the application server, wherein the application back-end performs server-side processing associated with the application;
(b) download to the client an application front-end, wherein the application front-end performs client-side processing associated with the application; and
(c) initiate the application front-end at the client.
25. The apparatus of claim 24, wherein the initiation mechanism further comprises:
(a) a loading mechanism configured to load the parameter-request panel into the single web page, wherein the parameter-request panel is active;
(b) the loading mechanism further configured to load the transaction-options panel into the single web page, wherein the transaction-options panel is inactive;
(c) the loading mechanism further configured to load the set of parameter-request fields into the parameter-request panel; and
(d) a presentation mechanism configured to present the single web page to the user at the client.
26. The apparatus of claim 23, wherein the presentation mechanism further comprises:
(a) a loading mechanism configured to load the set of transaction options into the transaction-options panel;
(b) the loading mechanism further configured to load data associated with each transaction option from the set of transaction options into the transaction-options panel; and
(c) a modification mechanism configured to make the transaction-options panel active without modifying the parameter-request panel.
27. The apparatus of claim 23, further comprising a replacement mechanism configured to replace the set of transaction options included in the transaction-options panel with detail information associated with the transaction-option selection.
28. The apparatus of claim 27, further comprising:
(a) the receiving mechanism further configured to receive a request to review the set of transaction options;
(b) a hiding mechanism configured to hide the transaction-completion panel;
(c) a restoring mechanism configured to restore the transaction-options panel to its original size, and
(d) the replacement mechanism further configured to replace the detail information associated with the transaction-option selection with the set of transaction options.
29. The apparatus of claim 27, further comprising an updating mechanism configured to update the detail information to include information associated with the transaction-completion information.
30. The apparatus of claim 23, wherein the presentation mechanism is further configured to:
(a) reduce the size of the transaction-options panel from its original size to a reduced size;
(b) load the transaction-completion panel into the single web page; and
(c) make the transaction-completion panel active without modifying the parameter-request panel and without making additional modifications to the transaction-options panel.
31. The apparatus of claim 23, wherein the completion mechanism is further configured to:
(a) finalize the transaction;
(b) create confirmation documents; and
(c) send the confirmation documents to the user.
32. The apparatus of claim 23, further comprising:
(a) the receiving mechanism further configured to receive new transaction parameters from the user;
(b) a modification mechanism configured to modify the set of transaction options to include a new set of transaction options associated with the new transaction parameters, and
(c) the modification mechanism further configured to modify the set of transaction-completion fields to include a new set of transaction-completion fields associated with the new set of transaction options.

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

1. A device for crimping an implant, in particular an intraluminal endoprosthesis, which can assume either a compressed state or an expanded state at least over a portion of the length thereof, characterized by a hollow-cylindrical andor hollow-conical, optionally braided wire netting, in an inner volume of which the implant in the expanded state can be placed, at least via a section thereof, wherein, upon application of a tensile force on at least one end in the longitudinal direction, andor upon application of a compressive force in the radial direction, the wire netting simultaneously undergoes extension and a reduction of the inner diameter such that the implant can be transformed, at least along a section thereof, from the expanded state into the compressed state.
2. The device according to claim 1, characterized in that the wire netting comprises a polymer or a metal alloy, optionally a stainless steel or cobalt-based alloy, the metal alloy optionally containing at least one element selected from the group consisting of Fe, Co, Cr and Ni.
3. The device according to claim 1, characterized in that the wire netting comprises a ring on at least one end in the direction of the longitudinal axis, the ring being displaceable relative to the other end of the wire netting in the longitudinal direction, optionally along a rail.
4. The device according to claim 1, characterized in that the device can be placed into a coolant.
5. A method for crimping an implant, in particular an intraluminal endoprosthesis, which can assume either a compressed state or an expanded state at least over a portion of the length thereof, optionally via the use of a device for crimping according to claim 1, the method having the following steps:
inserting at least a section of the implant, which is initially in the expanded state, into the inner volume of a hollow-cylindrical andor hollow-conical, optionally braided wire netting; and
reducing the inner diameter via application of a tensile force on at least one end of the wire netting in the longitudinal direction, andor a compressive force onto the wire netting in the radial direction such that the inserted implant is transformed from the expanded state into the compressed state, at least along a section.
6. The method according to claim 5, characterized in that the implant and, optionally the device for crimping, are cooled in a coolant to below a transition temperature before the implant is transformed into the compressed state.
7. The method according to claim 5, characterized in that, in order to apply a tensile force, a ring mounted at a first end of the wire netting in the longitudinal direction is displaced optionally on a rail relative to the stationary, opposing second end of the wire netting.
8. The method according to claim 5, characterized in that, after the transformation into the compressed state, the compressed section of the implant is inserted into a tubular outer shaft of a catheter.
9. The method according to claim 8, characterized in that the implant is also transformed into the compressed state in a second section, which was initially not inserted into the outer shaft, and is then inserted into the outer shaft.