What is claimed is:
1. A cartridge loaded in a gas-operated weapon selected from the group consisting of gas operated automatic and semiautomatic weapons, the cartridge comprising:
a cartridge case having a tubular shape with an open end, and oppositely disposed head, and a bore therebetween, the head having a primer cavity, a web separating the primer cavity from the bore, and a flash hole through the web;
a primer stored within said primer cavity;
a projectile disposed within the bore so as to close the open end of the cartridge case, the projectile having a weight of about 100 grains or more;
a charge cavity delimited within the bore between the web and the projectile; and
a propellant charge contained within the charge cavity in an amount sufficient to propel the projectile from the cartridge case at a subsonic speed and to recycle the weapon.
2. A cartridge according to claim 1, wherein the cartridge is a .223 caliber, and the charge cavity is sized to accommodate about 14 grains of the propellant charge.
3. A cartridge according to claim 1, wherein the projectile has a weight of up to about 130 grains.
4. A cartridge according to claim 1, wherein the propellant charge completely fills the charge cavity.
5. A cartridge according to claim 1, wherein the cartridge is a .308 caliber, the projectile weighs about 180 to about 300 grains, and the charge cavity is sized to accommodate about 14 to about 18 grains of the propellant charge.
6. A cartridge according to claim 5, wherein the propellant charge completely fills the charge cavity.
7. A cartridge according to claim 1, wherein the projectile has a specific gravity of greater than 11.7.
8. A cartridge according to claim 1, wherein the projectile has a caliber of from .22 to .50.
9. A cartridge according to claim 1, wherein the weapon has a barrel length of about 10 to about 16 inches.
10. A cartridge according to claim 1, wherein said projectile comprises at least one recess circumventing said projectile.
11. A cartridge according to claim 10 wherein said projectile comprises at least one ring adjacent to said recess.
12. A cartridge according to claim 11 wherein said projectile comprises three recesses and three rings.
13. A cartridge according to claim 11 wherein said ring is at least approximately 0.05 inches to no more than approximately 0.13 inches in width.
14. A cartridge according to claim 11 wherein said recess has a depth of at least approximately 0.003 inches to no more than approximately 0.010 inches.
15. A cartridge according to claim 14 wherein said depth is no more than approximately 0.006 inches.
16. A cartridge according to claim 12 wherein said projectile is at least approximately 114 grains to no more than approximately 135 grains.
17. A cartridge according to claim 16 wherein said projectile is approximately 123 grains.
18. A .223 caliber cartridge loaded in a recycling weapon having a gas-operated reciprocating bolt, the cartridge comprising:
a cartridge case having a tubular shape with an open end, an oppositely disposed head, and a bore therebetween, the head having a primer cavity, a web separating the primer cavity from the bore, and a flash hole through the web;
a primer stored within the primer cavity;
a projectile disposed within the bore so as to close the open end of the cartridge case, the projectile having a weight of about 130 grains;
a charge cavity delimited within the bore between the web and the projectile; and
about 14 grains of propellant charge that completely fills the charge cavity, the propellant charge within the charge cavity being an amount sufficient to propel the projectile from the cartridge case at a subsonic speed and to recycle the reciprocating bolt of the weapon.
19. A .223 caliber cartridge according to claim 18, wherein the recycling weapon is chosen from the group consisting of gas operated automatic and semiautomatic weapons.
20. A .223 caliber cartridge according to claim 19, wherein the weapon has a barrel length of about 10 to about 16 inches, and the amount of the propellant charge in the charge cavity is sufficient to procedure a pressure of about 45,000 psi to 51,000 psi when ignited to propel the projectile from the cartridge case.
21. A process of firing a cartridge from a gas-operated automatic or semiautomatic weapon, the process comprising the steps of:
providing a cartridge comprising:
a cartridge case having a tubular shape with an open end, an oppositely disposed head, and a bore therebewteen, the head having a primer cavity, a web separating the primer cavity from the bore, and a flash hole through the web;
a primer stored within the primer cavity;
a projectile disposed within the bore so as to close the open end of the cartridge case;
a charge cavity delimited within the bore between the web and the projectile; and
a propellant charge contained within the charge cavity in an amount sufficient to propel the projectile from the cartridge case at a subsonic speed;
loading the cartridge in a gas-operated weapon chosen from the group consisting of automatic and semiautomatic weapons having a reciprocating bolt; and then
firing the weapon by igniting the propellant charge, the propellant charge producing a chamber pressure sufficient to propel the projectile from the cartridge case at a subsonic speed and to recycle the reciprocating bolt of the weapon.
22. A process according to claim 21, wherein the charge cavity has a noncylindrical shape.
23. A process according to claim 21, wherein the charge cavity has a tapered shape.
24. A process according to a claim 21, wherein the charge cavity has a uniformly and continuously tapered shape.
25. A process according to claim 21, wherein the cartridge is a .223 caliber, the projectile weighs at least 100 grains, and the charge cavity is sized to accommodate not more than 14 grains of the propellant charge.
26. A process according to claim 25, wherein the propellant charge completely fills the charge cavity.
27. A process according to claim 21, wherein the cartridge is a .308 caliber, the projectile weighs about 180 to about 300 grains, and the charge cavity is sized to accommodate about 14 to about 18 grains of the propellant charge.
28. A process according to claim 27, wherein the propellant charge completely fills the charge cavity.
29. A process according to claim 21, wherein the projectile has a specific gravity of greater than 11.0.
30. A process according to claim 21, wherein the projectile has a caliber of from .22 to .50.
31. A process according to claim 21, wherein the weapon has a barrel length of about 10 to about 20 inches.
32. A process according to claim 21, wherein the cartridge is a .223 caliber, the projectile weights at least 100 grains, and the amount of the propellant charge present in the charge cavity is sufficient to produce a pressure of about 45,000 psi to 51,000 psi when ignited to propel the projectile from the cartridge case.
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. A method for Uniform Resource Locator (URL) filtering, comprising:
receiving an event notification upon the occurrence of an event associated with a received URL;
searching, in response to said event notification, a lexical search tree data structure storing a plurality of URLs for said received URL; and
processing said received URL in response to said received URL not matching any of said plurality of URLs stored in said lexical search tree data structure.
2. The method of claim 1, wherein said searching said lexical search tree comprises:
determining a hash value for said received URL;
determining a branch associated with a root node of said lexical search tree data structure corresponding to said hash value, said branch along with said root node representing at least one URL of said plurality of URLs, said branch having one or more leaf nodes linked hierarchically to one another, each leaf node representing an element of said at least one URL; and
traversing only said branch to find a match between said at least one URL and said received URL.
3. The method of claim 2, wherein said determining a hash value comprises:
determining a first element of said received URL; and
determining a hash value for said first element.
4. The method of claim 3, said hash value being the ASCII code for said first element.
5. The method of claim 2, wherein said traversing only said branch comprises comparing successive elements of said received URL with successive elements of said at least one URL stored in successive leaf nodes of said one or more leaf nodes so long as said successive elements of said received URL match said successive elements of said at least one URL.
6. The method of claim 2, wherein said traversing only said branch further comprises:
determining a twig associated with said branch at a point of divergence between said at least one URL and said received URL, said twig representing a terminating substring of a second URL of said plurality of URLs; and
traversing said twig to find a match between a terminating substring of said received URL and said terminating substring represented by said twig.
7. The method of claim 6, wherein said traversing said twig comprises comparing successive elements of said terminating substring of said received URL with successive elements of said terminating substring of said second URL represented by said twig so long as said successive elements match.
8. The method of claim 5, wherein said traversing only said branch further comprises:
setting a current node pointer to point to a leaf node of said one or more leaf nodes;
setting a target signature pointer to point to an element of said received URL;
in response to a value of said leaf node pointed to by said current node pointer being equal to a wild card character and a value of the element pointed to by said target signature pointer being equal to a value of the next leaf node following the leaf node pointed to by said current node pointer, updating said current node pointer to point to a leaf node following said next leaf node.
9. The method of claim 1, wherein said receiving said event notification comprises receiving said event notification upon the occurrence of an event selected from the group consisting of a URL map event and a receive raw data event.
10. A system for Uniform Resource Locator (URL) filtering, comprising:
a web server operable to receive a URL request from a client; and
a filter operable, upon receiving an event notification relating to said URL request from said web server, to search a lexical search tree data structure storing a plurality of URLs for said received URL, said filter further operable to process said received URL in response to said received URL not matching any of said plurality of URLs.
11. The system of claim 10, wherein said event notification relates to an event selected from the group consisting of a URL map event and a receive raw data event.
12. The system of claim 10, further comprising:
a computer readable medium with computer program logic recorded thereon for searching said lexical search tree data structure, said computer readable medium comprising:
means for determining a hash value for said received URL;
means for determining a branch associated with a root node of said lexical search tree data structure corresponding to said hash value, said branch along with said root node representing at least one URL of said plurality of URLs, said branch having one or more leaf nodes linked hierarchically to one another, each leaf node representing an element of said at least one URL; and
means for traversing only said branch to find a match between said at least one URL and said received URL.
13. The system of claim 12, wherein said means for determining a hash value comprises:
means for determining a first element of said received URL; and
means for determining a hash value for said first element.
14. The system of claim 13, wherein said means for traversing only said branch comprises means for comparing successive elements of said received URL with successive elements of said at least one URL stored in successive leaf nodes of said one or more leaf nodes so long as said successive elements of said received URL match said successive elements of said at least one URL.
15. The system of claim 14, wherein said means for traversing only said branch further comprises:
means for determining a twig associated with branch at a point of divergence between said at least one URL and said received URL, said twig representing a terminating substring of a second URL of said plurality of URLs; and
means for traversing said twig to find a match between a terminating substring of said received URL and said terminating substring represented by said twig.
16. The system of claim 15, wherein said means for traversing said twig comprises means for comparing successive elements of said terminating substring of said received URL with successive elements of said terminating substring of said second URL represented by said twig so long as said successive elements match.
17. A method for Uniform Resource Locator (URL) filtering, comprising:
receiving an event notification from a web server upon the occurrence of a URL map event;
determining, in response to receiving said event notification, a hash value for a URL received by said web server from a client;
determining a branch associated with a root node of a lexical search tree data structure corresponding to said hash value, said lexical search tree data structure storing a plurality of URLs, said branch along with said root node representing at least one URL of said plurality of URLs, said branch having one or more leaf nodes linked hierarchically to one another, each leaf node representing an element of said at least one URL;
traversing only said branch to find a match between said received URL and said at least one URL; and
processing said received URL in response to said received URL not matching said at least one URL.
18. The system of claim 17, said receiving said event notification comprising receiving a notification parameter from said web server, said notification parameter pointing to a data structure storing said received URL.
19. The system of claim 17, further comprising notifying said web server of a match between said received URL and said at least one URL.
20. The system of claim 17, further comprising:
registering with a web server to receive notification upon the occurrence of said URL map event.