Author: claimsbot

1. A method of replicating data for a distributed database between a plurality of instances, each instance comprising one or more server computers with memory and one or more processors, the method comprising:
identifying a first instance of the distributed database at a first geographic location;
identifying a second instance of the distributed database at a second geographic location;
tracking changes to the distributed database at the first instance by storing deltas, each delta having a row identifier that identifies a piece of data modified, a sequence identifier that specifies an order in which the deltas are applied to the data, and an instance identifier that specifies an instance where the delta was created;
determining which deltas are to be sent to the second instance using a second egress map at the first instance, wherein the second egress map specifies which combinations of row identifier and sequence identifier have been acknowledged as received at the second instance;
building a second transmission matrix for the second instance that identifies deltas that have not yet been acknowledged as received at the second instance;
transmitting deltas identified in the second transmission matrix to the second instance;
receiving acknowledgement that transmitted deltas have been incorporated in the second instance; and
updating the second egress map to indicate acknowledged deltas.
2. The method of claim 1, further comprising:
identifying a third instance of the distributed database at a third geographic location distinct from the first and second geographic locations;
determining which deltas are to be sent to the third instance using a third egress map at the first instance, wherein the third egress map specifies which combinations of row identifier and sequence identifier have been acknowledged as received at the third instance;
building a third transmission matrix for the third instance that identifies deltas that have not yet been acknowledged as received at the third instance;
modifying the transmission matrices for the second and third instances to form one or more revised transmission matrices, wherein deltas identified in each revised transmission matrix are transmitted to a respective location to update the instance at the respective location, and deltas identified in at least one of the revised transmission matrices are transmitted to the second location for subsequent transmission from the second location to the third location;
receiving acknowledgement that deltas transmitted to the third instance, either directly or indirectly via the second instance, have been incorporated in the third instance; and
updating the third egress map to indicate acknowledged deltas.
3. The method of claim 2, including assigning a cost for transmissions between pairs of geographic locations, and wherein modifying the transmission matrices includes an analysis of the total cost for transmitting the deltas to the second and third geographic locations.
4. The method of claim 2, wherein modifying the transmission matrices includes determining bandwidth availability between geographic locations of the instances.
5. The method of claim 2, wherein the transmission matrices for the second and third instances are the same, there is only one revised transmission matrix, the one revised transmission matrix is the same as the transmission matrices, and deltas identified in the revised transmission matrix are transmitted to the second geographic location for subsequent transmission to the third geographic location.
6. The method of claim 1, wherein each sequence identifier comprises a timestamp and a unique tie breaker value that is assigned based on hardware andor software at each instance of the distributed database.
7. The method of claim 1, wherein the second geographic location is distinct from the first geographic location
8. A method of compacting a distributed database having a plurality of instances, wherein each instance stores data on one or more server computers and each server computer has memory and one or more processors, the method comprising:
identifying a first instance of the distributed database;
selecting a set of one or more row identifiers that identify rows of data in the distributed database, wherein each row in the distributed database has a base value and a set of zero or more deltas, and wherein each delta specifies a change to the base value, includes a sequence identifier that specifies an order in which the deltas are to be applied to the base value, and specifies an instance where the delta was created;
selecting a compaction horizon for the selected set of one or more row identifiers, wherein the compaction horizon is a sequence identifier;
applying, in sequence, all deltas for the selected set of one or more row identifiers that have sequence identifiers less than or equal to the compaction horizon, to the base value for the corresponding row identifier; and
deleting the deltas that have been applied to the base value for the corresponding row identifier.
9. The method of claim 8, further comprising:
identifying a plurality of other instances of the distributed database;
wherein the selected compaction horizon for the selected set of one or more row identifiers satisfies:
all deltas that
(i) were created at the first instance,
(ii) are for rows corresponding to row identifiers in the selected set of one or more row identifiers, and
(iii) have sequence identifiers less than or equal to the compaction horizon,

have been transmitted to and acknowledged by all of the other instances that maintain data for the corresponding row identifiers; and
all deltas that
(i) were created at instances in the plurality of other instances,
(ii) are for rows corresponding to row identifiers in the selected set of one or more row identifiers, and
(iii) have sequence identifiers less than or equal to the compaction horizon,

have been received at the first instance.
10. The method of claim 8, wherein each sequence identifier comprises a timestamp and a unique tie breaker value that is assigned based on hardware andor software at each instance of the distributed database.
11. A method of reading a data item from a distributed database with a plurality of data items, each data item comprising a base value and zero or more deltas that specify modifications to the base value, the method performed by one or more server computers having memory and one or more processors, the method comprising:
receiving a request from a client for a specified data item, the request including a row identifier that identifies the data item;
reading the base value for the specified data item from the distributed database and storing the base value in memory;
reading the deltas for the specified data item, if any, from the distributed database, wherein each delta includes a sequence identifier that specifies an order in which the deltas are to be applied to the base value;
applying the deltas to the base value in memory, in sequence, resulting in a current base value stored in memory; and
returning the current base value stored in memory to the client.
12. A server system, comprising a plurality of servers, each server having:
one or more processors;
memory; and
one or more programs stored in the memory for execution by the one or more processors, the one or more programs comprising instructions for:
identifying a first instance of the distributed database at a first geographic location;
identifying a second instance of the distributed database at a second geographic location;
tracking changes to the distributed database at the first instance by storing deltas, each delta having a row identifier that identifies a piece of data modified, a sequence identifier that specifies an order in which the deltas are applied to the data, and an instance identifier that specifies an instance where the delta was created;
determining which deltas are to be sent to the second instance using a second egress map at the first instance, wherein the second egress map specifies which combinations of row identifier and sequence identifier have been acknowledged as received at the second instance;
building a second transmission matrix for the second instance that identifies deltas that have not yet been acknowledged as received at the second instance;
transmitting deltas identified in the second transmission matrix to the second instance;
receiving acknowledgement that transmitted deltas have been incorporated in the second instance; and
updating the second egress map to indicate acknowledged deltas.
13. The server system of claim 12, further comprising instructions for:
identifying a third instance of the distributed database at a third geographic location distinct from the first and second geographic locations;
determining which deltas are to be sent to the third instance using a third egress map at the first instance, wherein the third egress map specifies which combinations of row identifier and sequence identifier have been acknowledged as received at the third instance;
building a third transmission matrix for the third instance that identifies deltas that have not yet been acknowledged as received at the third instance;
modifying the transmission matrices for the second and third instances to form one or more revised transmission matrices, wherein deltas identified in each revised transmission matrix are transmitted to a respective location to update the instance at the respective location, and deltas identified in at least one of the revised transmission matrices are transmitted to the second location for subsequent transmission from the second location to the third location;
receiving acknowledgement that deltas transmitted to the third instance, either directly or indirectly via the second instance, have been incorporated in the third instance; and
updating the third egress map to indicate acknowledged deltas.
14. The server system of claim 13, wherein the transmission matrices for the second and third instances are the same, there is only one revised transmission matrix, the one revised transmission matrix is the same as the transmission matrices, and deltas identified in the revised transmission matrix are transmitted to the second geographic location for subsequent transmission to the third geographic location.
15. A server system, comprising a plurality of servers, each server having:
one or more processors;
memory; and
one or more programs stored in the memory for execution by the one or more processors, the one or more programs comprising instructions for:
identifying a first instance of a distributed database;
selecting a set of one or more row identifiers that identify rows of data in the distributed database, wherein each row in the distributed database has a base value and a set of zero or more deltas, and wherein each delta specifies a change to the base value, includes a sequence identifier that specifies an order in which the deltas are to be applied to the base value, and specifies an instance where the delta was created;
selecting a compaction horizon for the selected set of one or more row identifiers, wherein the compaction horizon is a sequence identifier;
applying, in sequence, all deltas for the selected set of one or more row identifiers that have sequence identifiers less than or equal to the compaction horizon, to the base value for the corresponding row identifier; and
deleting the deltas that have been applied to the base value for the corresponding row identifier.
16. The server system of claim 15, further comprising instructions for:
identifying a plurality of other instances of the distributed database;
wherein the selected compaction horizon for the selected set of one or more row identifiers satisfies:
all deltas that
(i) were created at the first instance,
(ii) are for rows corresponding to row identifiers in the selected set of one or more row identifiers, and
(iii) have sequence identifiers less than or equal to the compaction horizon,

have been transmitted to and acknowledged by all of the other instances that maintain data for the corresponding row identifiers; and
all deltas that
(i) were created at instances in the plurality of other instances,
(ii) are for rows corresponding to row identifiers in the selected set of one or more row identifiers, and
(iii) have sequence identifiers less than or equal to the compaction horizon,

have been received at the first instance.
17. A server system, comprising a plurality of servers, each server having:
one or more processors;
memory; and
one or more programs stored in the memory for execution by the one or more processors, the one or more programs comprising instructions for:
receiving a request from a client for a specified data item from a distributed database with a plurality of data items, each data item comprising a base value and zero or more deltas that specify modifications to the base value, wherein the request includes a row identifier that identifies the data item;
reading the base value for the specified data item from the distributed database and storing the base value in memory;
reading the deltas for the specified data item, if any, from the distributed database, wherein each delta includes a sequence identifier that specifies an order in which the deltas are to be applied to the base value;
applying the deltas to the base value in memory, in sequence, resulting in a current base value stored in memory; and
returning the current base value stored in memory to the client.
18. A computer readable storage medium storing one or more programs configured for execution by a server computer system having one or more processors and memory storing one or more programs for execution by the one or more processors, the one or more programs comprising instructions to:
identify a first instance of the distributed database at a first geographic location;
identify a second instance of the distributed database at a second geographic location;
track changes to the distributed database at the first instance by storing deltas, each delta having a row identifier that identifies a piece of data modified, a sequence identifier that specifies an order in which the deltas are applied to the data, and an instance identifier that specifies an instance where the delta was created;
determine which deltas are to be sent to the second instance using a second egress map at the first instance, wherein the second egress map specifies which combinations of row identifier and sequence identifier have been acknowledged as received at the second instance;
build a second transmission matrix for the second instance that identifies deltas that have not yet been acknowledged as received at the second instance;
transmit deltas identified in the second transmission matrix to the second instance;
receive acknowledgement that transmitted deltas have been incorporated in the second instance; and
update the second egress map to indicate acknowledged deltas.
19. The computer readable storage medium of claim 18, further comprising instructions to:
identify a third instance of the distributed database at a third geographic location distinct from the first and second geographic locations;
determine which deltas are to be sent to the third instance using a third egress map at the first instance, wherein the third egress map specifies which combinations of row identifier and sequence identifier have been acknowledged as received at the third instance;
build a third transmission matrix for the third instance that identifies deltas that have not yet been acknowledged as received at the third instance;
modify the transmission matrices for the second and third instances to form one or more revised transmission matrices, wherein deltas identified in each revised transmission matrix are transmitted to a respective location to update the instance at the respective location, and deltas identified in at least one of the revised transmission matrices are transmitted to the second location for subsequent transmission from the second location to the third location;
receive acknowledgement that deltas transmitted to the third instance, either directly or indirectly via the second instance, have been incorporated in the third instance; and
update the third egress map to indicate acknowledged deltas.
20. The computer readable storage medium of claim 19, wherein the transmission matrices for the second and third instances are the same, there is only one revised transmission matrix, the one revised transmission matrix is the same as the transmission matrices, and deltas identified in the revised transmission matrix are transmitted to the second geographic location for subsequent transmission to the third geographic location.
21. A computer readable storage medium storing one or more programs configured for execution by a server computer system having one or more processors and memory storing one or more programs for execution by the one or more processors, the one or more programs comprising instructions to:
identify a first instance of a distributed database;
select a set of one or more row identifiers that identify rows of data in the distributed database, wherein each row in the distributed database has a base value and a set of zero or more deltas, and wherein each delta specifies a change to the base value, includes a sequence identifier that specifies an order in which the deltas are to be applied to the base value, and specifies an instance where the delta was created;
select a compaction horizon for the selected set of one or more row identifiers, wherein the compaction horizon is a sequence identifier;
apply, in sequence, all deltas for the selected set of one or more row identifiers that have sequence identifiers less than or equal to the compaction horizon, to the base value for the corresponding row identifier; and
delete the deltas that have been applied to the base value for the corresponding row identifier.
22. The computer readable storage medium of claim 21, further comprising instructions to:
identify a plurality of other instances of the distributed database;
wherein the selected compaction horizon for the selected set of one or more row identifiers satisfies:
all deltas that
(i) were created at the first instance,
(ii) are for rows corresponding to row identifiers in the selected set of one or more row identifiers, and
(iii) have sequence identifiers less than or equal to the compaction horizon,

have been transmitted to and acknowledged by all of the other instances that maintain data for the corresponding row identifiers; and
all deltas that
(i) were created at instances in the plurality of other instances,
(ii) are for rows corresponding to row identifiers in the selected set of one or more row identifiers, and
(iii) have sequence identifiers less than or equal to the compaction horizon,

have been received at the first instance.
23. A computer readable storage medium storing one or more programs configured for execution by a server computer system having one or more processors and memory storing one or more programs for execution by the one or more processors, the one or more programs comprising instructions to:
receive a request from a client for a specified data item from a distributed database with a plurality of data items, each data item comprising a base value and zero or more deltas that specify modifications to the base value, wherein the request includes a row identifier that identifies the data item;
read the base value for the specified data item from the distributed database and storing the base value in memory;
read the deltas for the specified data item, if any, from the distributed database, wherein each delta includes a sequence identifier that specifies an order in which the deltas are to be applied to the base value;
apply the deltas to the base value in memory, in sequence, resulting in a current base value stored in memory; and
return the current base value stored in memory to the client.

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 compound of general formula (I),
any of its enantiomers or any mixture of its enantiomers, or a pharmaceutically acceptable salt thereof,
wherein
Q is \u2014CH2\u2014CH2\u2014 or \u2014CH2\u2014CH2\u2014CH2\u2014;
one of R1 and R2 is \u2014CH2\u2014CH2\u2014CH2\u2014R3, \u2014CH2\u2014CH\u2550CH\u2014R3, or \u2014CH2\u2014C\u2261C\u2014R3;
wherein R3 is aryl or heteroaryl;
which aryl and heteroaryl is optionally substituted with one or more substituents selected from the group consisting of:
halogen, hydroxy, amino, cyano, nitro, trifluoromethyl, alkoxy, cycloalkoxy, alkyl, cycloalkyl, cycloalkylalkyl, alkenyl, and alkynyl; and
the other of R1 and R2 is \u2014CO\u2014R4;
wherein R4 is alkyl, cycloalkyl, cycloalkylalkyl, aryl, or arylalkyl.
2. The compound according to claim 1, wherein
Q is \u2014CH2\u2014CH2\u2014.
3. The compound according to claim 1, wherein
Q is \u2014CH2\u2014CH2\u2014CH2\u2014.
4. The compound according to claim 1, wherein one of R1 and R2 is \u2014CH2\u2014CH\u2550CH\u2014R3;
wherein R3is defined as in claim 1.
5. The compound according to claim 1, wherein R4 is alkyl.
6. The compound according to claim 1, wherein
Q is \u2014CH2\u2014CH2\u2014 or \u2014CH2\u2014CH2\u2014CH2\u2014;
one of R1 and R2 is \u2014CH2\u2014CH\u2550CH\u2014R3, or \u2014CH2\u2014C\u2261C\u2014R3;
wherein R3is phenyl; and
the other of R1 and R2 is \u2014CO\u2014R4;
wherein R4 is alkyl.
7. A compound of claim 1 which is
(\xb1)-1-9-(3-Phenyl-allyl)-3,9-diaza-bicyclo4.2.1non-3-yl-propan-1-one;
(\xb1)-1-10-(3-Phenyl-allyl)-3,10-diaza-bicyclo4.3.1dec-3-yl-propan-1-one;
(\xb1)-1-3-(3-Phenyl-allyl-3,9-diazabicyclo4.2.1non-9-yl-propan-1-one;
or any of its enantiomers or any mixture of its enantiomers, or a pharmaceutically acceptable salt thereof.
8. A pharmaceutical composition, comprising a therapeutically effective amount of a compound of claim 1, or any of its enantiomers or any mixture of its enantiomers, or a pharmaceutically acceptable salt thereof, together with at least one pharmaceutically acceptable carrier, excipient or diluent.
9. A method for treatment, prevention or alleviation of a disease or a disorder or a condition of a living animal body, including a human, which disorder, disease or condition is responsive to responsive to modulation of the opioid receptor, which method comprises the step of administering to such a living animal body in need thereof a therapeutically effective amount of a compound according to claim 1, or any of its enantiomers or any mixture of its enantiomers, or a pharmaceutically acceptable salt thereof.
10. The method according to claim 9, wherein the disease, disorder or condition responsive to modulation of the opioid receptor is pain, postoperative pain, chronic pain, cancer pain, neuropathic pain, pain during labour and delivery, drug addiction, heroin addiction, cocaine addiction, alcoholism, irritable bowel syndrome, constipation, nausea, vomiting, pruritic dermatoses, allergic dermatitis, atopy, eating disorders, opiate overdoses, depression, smoking, sexual dysfunction, shock, stroke, spinal damage, or head trauma.
11. (canceled)

1. Apparatus for applying a signature or other written date to a file or document created, stored andor displayed in html format, the apparatus comprising means for capturing said hand written data in a first data format, means for converting said hand written data into Html format and means for applying said hand written data in html format in said file or document.
2. Apparatus according to claim 1, wherein said hand written data is captured in an image file format.
3. Apparatus according to claim 1, wherein said means for creating and capturing the hand written data comprises a pen-based input strip.
4. Apparatus according to claim 1, comprising means for attaching a key or link into a software package for creating and transmitting documents in html format.
5. Apparatus according to claim 4, wherein said key or link creates an additional option within the software package which, when selected, retrieves the hand written data created on the input strip and captured electronically in image file format, converts the data from an image file to html format, and adds the hand written data to an html document in a user-defined position.
6. Apparatus according to claim 5, wherein said apparatus calls for the hand written data to be created and captured when the key or link is selected and then substantially immediately converts it to html format and adds it to the html document.
7. Apparatus according to claim 1, including means for creating an encryptive code number associated with hand written data which has been created, captured and converted to html format.
8. Apparatus according to claim 7, wherein said encryptive code is arranged to carry information which permits one or more of the following:
a) to produce a visual representation of the signature when decoded (i.e. to allow visual verification by the recipient);
b) to allow a more rigorous comparison of the key characteristics of the signature with a signature previously received from the same sender (i.e. the encrypted code number comprises an encrypted digitised summary of the key characteristics of the incoming signature which can be compared with the encrypted code number associated with a signature previously received from the same sender, and the probability that the writer of the two signatures is the same person can be calculated and displayed);
c) to display the date andor time on the sender’s PC when the handwritten data was added to the document (e.g. when it was signed);
d) to display the date and time on a remote internet server when the handwritten data was added to the document (e.g. when it was signed) if the sender was logged onto the Internet at the time of signature (it should be borne in mind that the encrypted code number might indicate the date and time that the handwritten data was added to the document in the case where it was converted to html format and added to the document in real time, and in the case where a stored image file is converted to html format and added to the document);
e) to display an indication as to whether or not the document has been changed since the handwritten date (e.g. signature) was added;
f) to utilise an optional PIN or security code number (for example, a 5-digit base code) which can be incorporated into the encrypted code number and which has been pre-agreed between two or more parties (for example, verbally), such that the handwritten data (e.g. signature) cannot be visually reproduced and a comparison between the signature and a previously-stored handwritten date (e.g. signature) cannot be performed without the recipient having entered the pre-agreed security code number. It is envisaged the apparatus could be supplied with a default security code number which can be changed by the user(s) if this feature is required to be utilised.
9. A method for applying a signature or other hand written data to a file or document created, stored andor displayed in Html format, the method comprising the steps of capturing the hand written data in a first data format, converting said hand written data into html format, and applying said hand written data in html format to said file or document.

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

What is claimed is:

1. An optical semiconductor device, comprising:
a first conduction type substrate;
an active layer formed in a stripe over the first conduction type substrate;
a mesa shaped burying layer formed around the active layer and having a larger band gap than that of the active layer; and
a groove that electrically isolates the burying layer,
wherein the section of the burying layer is in an inverse trapezoid shape of which the upper base side is longer than the lower base side.
2. The optical semiconductor device as set forth in claim 1,
wherein the burying layer has a laminated structure of the first conduction type semiconductor layer and a second condition type semiconductor layer.
3. The optical semiconductor device as set forth in claim 2,
wherein the carrier concentrations of the first conduction type semiconductor layer and the second conduction type semiconductor layer are larger than 11017 cm3, respectively.
4. The optical semiconductor device as set forth in claim 1,
wherein a stopping layer for etching is disposed on a bottom face of the groove.
5. The optical semiconductor device as set forth in claim 1, further comprising a resin layer formed in the groove.
6. The optical semiconductor device as set forth in claim 5,
wherein the resin includes benzocyclobutene resin.
7. The optical semiconductor device as set forth in claim 5,
wherein the upper surface of the resin layer is lower than the upper surface of the burying layer, and
further comprising a floating wiring portion formed over the groove.
8. The optical semiconductor device as set forth in claim 1,
wherein no substance is filled in the groove, and
further comprising a floating wiring portion formed over the groove.
9. An optical semiconductor device, comprising:
a first conduction type substrate;
an active layer formed over the first conduction type substrate;
a current confinement layer formed in a ridge stripe on the active layer;
a groove that electrically isolates the current confinement layer, the groove having a space portion; and
a floating wiring portion formed over the groove.
10. An optical semiconductor device, comprising:
a first conduction type substrate;
an active layer formed on the first conduction type substrate; and
a mesa shaped current confinement layer formed on the active layer,
wherein a floating wiring portion is formed around the current confinement layer.
11. A method for fabricating an optical semiconductor device, comprising:
preparing a first conduction type substrate;
forming an active layer in a stripe on the first conduction type substrate;
forming a burying layer around the active layer, the burying layer having a band gap larger than that of the active layer;
forming grooves that isolate the burying layer in a stripe so as to form the section of the burying layer in an inverse trapezoid shape of which the upper base side is longer than the lower base side;
forming a resin layer filled in the groove;
forming wiring on the resin layer; and
selectively etching the resin layer so as to remove all or part of the resin layer and form a space portion in the groove below the wiring.
12. A method for fabricating an optical semiconductor device, comprising:
preparing a first conduction type substrate;
forming an active layer on the first conduction type substrate;
forming a current confinement layer on the active layer;
forming a resin layer filled around the current confinement layer;
forming wiring on the resin layer; and
selectively etching the resin layer so as to remove all or part of the resin layer and form a space portion below the wiring.