1. A molded lens for use in an optical pickup device, said molded lens comprising:
(a) a plane of incidence including a first optical surface;
(b) a plane of emergence including a second optical surface provided on an opposite side of the molded lens with respect to the plane of incidence; and
(c) an outer circumference surface having a shape formed by: (i) a first straight line portion which is substantially parallel to a plane including an optical axis of the molded lens, (ii) a second straight line portion which is substantially parallel with the first straight line portion and is symmetric with the first straight line portion about the plane including the optical axis of the molded lens, and (iii) two circular arcs each connecting end portions of the first and second straight line portions;
wherein a flash projects from a side of at least one of the two circular arc portions at at least one position apart from a point of intersection where a straight line that perpendicularly crosses the optical axis and that is parallel to the first and second straight line portions intersects the corresponding circular arc portion, and wherein the flash does not project past a line that is tangent to the corresponding circular arc portion at the point of intersection.
2. The molded lens of claim 1, wherein a length of the flash in a direction of the optical axis is not more than 0.03 mm.
3. The molded lens of claim 1, wherein the flash is formed on one side of the at least one the circular arc portion with respect to the point of intersection.
4. A molding die for molding the molded lens according to in claim 1, said molding die comprising:
(a) a first molding die for molding a portion of the molded lens including the plane of incidence thereof; and
(b) a second molding die for molding a portion of the molded lens including the plane of emergence thereof;
wherein an air vent port is formed in one of the first molding die and the second molding die.
5. A molded lens for an optical pickup device, comprising:
(a) a plane of incidence including a first optical surface;
(b) a plane of emergence including a second optical surface provided on an opposite side of the molded lens with respect to the plane of incidence; and
(c) a flange portion at a periphery of the plane of incidence and a periphery of the plane of emergence;
wherein a reference surface for positioning the molded lens is formed by one of: a surface of the flange portion on a side of the plane of incidence and a surface of the flange portion on a side of the plane of emergence, and wherein the reference surface projects from a corresponding one of the plane of incidence and the plane of emergence in an optical axis direction of the molded lens;
wherein a flash projects from the molded lens from the side of the one of the plane of incidence and the plane of emergence corresponding to the reference surface, said flash being generated between a sleeve and a core of a molding die for forming the molded lens, and said core staying in contact with the molded lens after injection molding and being movable with respect to the sleeve to push the molded lens out of the molding die; and
wherein the reference surface projects farther in the optical axis direction than the flash.
6. A molding die for molded lens for molding the molded lens described in claim 5, comprising:
(a) a first molding die for molding a portion of the molded lens including the plane of incidence thereof; and
(b) a second molding die for molding a portion of the molded lens including the plane of emergence thereof;
wherein one of the first molding die and the second molding die comprises the sleeve and the core.
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 method of providing recovery in a computer system, comprising:
intercepting events comprising at least one of a plurality of method calls, component activations, and component deactivations;
logging the events during execution of stateful piece-wise deterministic (PWD) components having a component state;
detecting a failure of one of the components based on an error detected during execution; and
replaying the logged events to transparently and automatically recover the component state.
2: The method of claim 1, further comprising:
intercepting non-deterministic events;
providing a policy mechanism that, upon interception of the events, permits the logging of the intercepted events;
providing an error handler that is invoked when an error is detected, such error handler being capable of masking the error from the component.
3: The method of claim 1, further comprising:
logging information about how the component is mapped to a first set of resources such that the component can be re-mapped to a different set of resources should a system failure result in a termination of the first set of resources, said re-mapping enabling scalability and load balancing.
4: The method of claim 3, wherein the information includes a logical identifier for the component that identifies logged state information for the component.
5: The method of claim 1, further comprising exactly-once execution comprising:
uniquely identifying messages at a sender;
detecting an original message and at least one duplicate message at a receiver;
eliminating the at least one duplicate message; and
providing a reply to the at least one duplicate message that is the same as a reply to the original message.
6: The method of claim 1, further comprising:
notifying an error handler when the error is detected;
contacting a recovery manager to recover the component that has failed;
re-trying an interaction that failed at the time of the failure; and
returning the result of the re-tried interaction to the component.
7 (Cancelled)
8: The method of claim 1, further comprising:
retrieving information related to the failed call; and
identifying the component based on the retrieved information.
9: The method of claim 1, further comprising:
updating references to the component with an interface pointer corresponding to the component; and
logging the recovery of the component.
10: The method of claim 1, further comprising verifying that the component state has not already been recovered prior to recovering the component state.
11: The method of claim 1, further comprising intercepting the method call and response, and invoking a policy on at least one of the call and the response.
12: The method of claim 1, wherein the computer system comprises a client and a server, and detecting the failure of the component comprises the client or server detecting the failure, and further comprising a component runtime associated with the client invoking an error handler associated with the client and providing information related to the failed call to the error handler.
13: The method of claim 12, further comprising identifying a recovery manager responsible for the component and passing the information to the recovery manager.
14 (Cancelled)
15: A system for providing recovery in a computer system, comprising:
a storage device that logs events comprising at least one of a plurality of method calls, component activations, and component deactivations during execution of stateful piece-wise deterministic (PWD) components having a component state;
a component runtime that receives the events from the storage device;
a error handler that receives the events from the component runtime and identifies the component based on the events; and
a recovery manager that receives the events from the storage device and replays the events to transparently and automatically recover the component state.
16: The system of claim 15, wherein the error handler is notified of an error and contacts the recovery manager to recover the component state.
17: The system of claim 15, wherein the recovery manager logs the recovery of the component state in the storage device, verifies that the component state has not already been recovered prior to recovering the component state, and communicates to the error handler additional information about the component.
18: The system of claim 15, wherein the component runtime intercepts the at least one method call and invokes a policy on the at least one method call.
19: The system of claim 15, further comprising an activation hook that logs information in the storage device that is sufficient to re-create the component.
20-23 (Cancelled)
24: A computer readable medium having computer-executable instructions for performing the steps comprising:
intercepting events comprising at least one of a plurality of method calls, component activations, and component deactivations;
logging the events during execution of at least one stateful piece-wise deterministic (PWD) component having a component state in a computer system;
detecting a failure of one of the components based on an error detected during execution; and
replaying the logged events to transparently and automatically recover the component state.
25: The computer readable medium of claim 24, having further computer-executable instructions for:
intercepting non-deterministic events;
providing a policy mechanism that, upon interception of the events, permits the logging of the intercepted events;
providing an error handler that is invoked when an error is detected, such error handler being capable of masking the error from the component.
26: The computer readable medium of claim 24, having further computer-executable instructions for:
logging information about how the component is mapped to a first set of resources such that the component can be re-mapped to a different set of resources should a system failure result in a termination of the first set of resources, said re-mapping enabling scalability and load balancing.
27: The computer readable medium of claim 26, wherein the information includes a logical identifier for the component that identifies logged state information for the component.
28: The computer readable medium of claim 24, having further computer-executable instructions for providing exactly-once execution comprising:
uniquely identifying messages at a sender;
detecting an original message and at least one duplicate message at a receiver;
eliminating the at least one duplicate message; and
providing a reply to the at least one duplicate message that is the same as a reply to the original message.
29: The computer readable medium of claim 24, having further computer-executable instructions for:
notifying an error handler when the error is detected;
contacting a recovery manager to recover the component that has failed;
re-trying an interaction that failed at the time of the failure; and
returning the result of the re-tried interaction to the component.
30 (Cancelled)
31: The computer readable medium of claim 24, having further computer-executable instructions for:
retrieving information related to the failed call; and
identifying the component based on the retrieved information.
32: The computer readable medium of claim 24, having further computer-executable instructions for:
updating references to the component with an interface pointer corresponding to the component; and
logging the recovery of the component.
33: The computer readable medium of claim 24, having further computer-executable instructions for verifying that the component state has not already been recovered prior to recovering the component state.