that will reliably
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 49
SubEthaSMTP 1.2.1
SubEthaSMTP is an easy to understand Java library that provides a receptive SMTP server component. more>>
SubEthaSMTP is an easy to understand Java library that provides a receptive SMTP server component.
By plugging this component into your Java application, you can easily receive SMTP mail using a simple abstract Java interface.
Also included is a small sub-project called Wiser, an easy to use incoming mail testing framework.
Main features:
- A mailing list manager (ie, SubEtha Mail)
- A mail server that delivers mail to user inboxes
- A mail archiver like Mail Archive
- An email test harness (Implemented in this project. Its called Wiser.)
SubEthaSMTP was split out of the SubEtha Mail mailing list manager because it is a useful standalone component. When we wrote SubEtha, the last thing we wanted to do was write our own SMTP server. In our search for a modular Java SMTP component, we examined:
Apache JAMES
JBoss Mail Server
Dumbster
Jsmtpd
JES
Java Mail Server
Since youre reading this page you probably already know what we found: Six different SMTP implementations without the slightest thought given to reusability. Even Jstmpd, which purports to be a "A Modular Java SMTP Daemon", isnt. Furthermore, even though JBoss Mail is in active development, the team was unintersted in componentization of the SMTP processing portion of their server.
During the development of SubEthas testing harness, we tried out the Dumbster software and found that not only was the API difficult to use, it did it not work properly, the developer has not done any development on it in about a year and it does not work reliably on Mac OS X. With two simple classes we re-implemented it as an included project called Wiser.
We hate reinventing wheels. This should be the LAST FREAKING JAVA SMTP IMPLEMENTATION.
Enhancements:
- This release fixes a couple of bugs with SMTP RFC handling.
<<lessBy plugging this component into your Java application, you can easily receive SMTP mail using a simple abstract Java interface.
Also included is a small sub-project called Wiser, an easy to use incoming mail testing framework.
Main features:
- A mailing list manager (ie, SubEtha Mail)
- A mail server that delivers mail to user inboxes
- A mail archiver like Mail Archive
- An email test harness (Implemented in this project. Its called Wiser.)
SubEthaSMTP was split out of the SubEtha Mail mailing list manager because it is a useful standalone component. When we wrote SubEtha, the last thing we wanted to do was write our own SMTP server. In our search for a modular Java SMTP component, we examined:
Apache JAMES
JBoss Mail Server
Dumbster
Jsmtpd
JES
Java Mail Server
Since youre reading this page you probably already know what we found: Six different SMTP implementations without the slightest thought given to reusability. Even Jstmpd, which purports to be a "A Modular Java SMTP Daemon", isnt. Furthermore, even though JBoss Mail is in active development, the team was unintersted in componentization of the SMTP processing portion of their server.
During the development of SubEthas testing harness, we tried out the Dumbster software and found that not only was the API difficult to use, it did it not work properly, the developer has not done any development on it in about a year and it does not work reliably on Mac OS X. With two simple classes we re-implemented it as an included project called Wiser.
We hate reinventing wheels. This should be the LAST FREAKING JAVA SMTP IMPLEMENTATION.
Enhancements:
- This release fixes a couple of bugs with SMTP RFC handling.
Download (0.77MB)
Added: 2007-06-29 License: LGPL (GNU Lesser General Public License) Price:
856 downloads
SpamTestBuddy 0.92
SpamTestBuddy is a simple, light-weight, multiple-input spam scoring tool. more>>
SpamTestBuddy is a simple, light-weight, multiple-input spam scoring tool. SpamTestBuddy project is standalone and can be used with simple procmail rules without root access or daemons. Features built-in support for simple DNS checks including DNSBL (DNS-based blocklist) queries, and can scan headers from filters such as SpamProbe, QSF, DSPAM that you already use.
The configuration is flexible and easy to edit in a human readable file. Different tests can add or remove from the total score.
(I am not trying to re-invent SpamAssassin. That is a very powerful piece of software with all the features you need. It is also somewhat large and is a greater challenge to install. SpamTestBuddy will just help you bring together existing scores from filters you already use, with a few useful extra tests thrown in. For an all-in-one solution, try SpamAssassin).
Tested under Linux, FreeBSD, and NetBSD.
COMMON USES
1) Combining more than one external filter:
If you have a number of filters that output a numeric probability or score, you can combine them together using +TestHeaderFloat and make a decision on the total (floating point) score. Examples of filters which integrate seamlessly are SpamProbe, QSF, DSPAM, CRM114.
2) Querying DNSBL (DNS based blocklists, real time lists) or local IP files:
Typically this is done by mail servers at the time of mail receipt. However, there are advantages to doing these "RBL" lookups later. SpamTestBuddy will let you query multiple real-time lists for fresh data on known spam sources, abusive networks, etc. You can combine the results with your other statistical body-reading filters. You can also use TestFileIP to look up the IP in a local text file, such as a custom whitelist or blacklist.
3) Reducing false positives from other filters:
You can use SpamTestBuddy as a secondary filter to interpret existing scores differently. Alternatively, you can make a more conservative configuration by combining scores. This may be helpful for revisiting classification errors
4) Parsing the IP address of the sender
The IP address of the SMTP server which relayed mail is always visible in the Received headers, but parsing and extracting the correct IP address is hard to do reliably with procmail recipes alone. SpamTestBuddy can pick out the correct address by applying SkipReceived, a list of networks you define to consider local and ignore. The resulting IP address is conveniently displayed in the new X-SpamTestBuddy header, simplifying your procmail recipes.
Enhancements:
- This is the first public release of this software.
- The configuration file was enhanced for ease of use.
- DNSBL (RBL) support was added.
<<lessThe configuration is flexible and easy to edit in a human readable file. Different tests can add or remove from the total score.
(I am not trying to re-invent SpamAssassin. That is a very powerful piece of software with all the features you need. It is also somewhat large and is a greater challenge to install. SpamTestBuddy will just help you bring together existing scores from filters you already use, with a few useful extra tests thrown in. For an all-in-one solution, try SpamAssassin).
Tested under Linux, FreeBSD, and NetBSD.
COMMON USES
1) Combining more than one external filter:
If you have a number of filters that output a numeric probability or score, you can combine them together using +TestHeaderFloat and make a decision on the total (floating point) score. Examples of filters which integrate seamlessly are SpamProbe, QSF, DSPAM, CRM114.
2) Querying DNSBL (DNS based blocklists, real time lists) or local IP files:
Typically this is done by mail servers at the time of mail receipt. However, there are advantages to doing these "RBL" lookups later. SpamTestBuddy will let you query multiple real-time lists for fresh data on known spam sources, abusive networks, etc. You can combine the results with your other statistical body-reading filters. You can also use TestFileIP to look up the IP in a local text file, such as a custom whitelist or blacklist.
3) Reducing false positives from other filters:
You can use SpamTestBuddy as a secondary filter to interpret existing scores differently. Alternatively, you can make a more conservative configuration by combining scores. This may be helpful for revisiting classification errors
4) Parsing the IP address of the sender
The IP address of the SMTP server which relayed mail is always visible in the Received headers, but parsing and extracting the correct IP address is hard to do reliably with procmail recipes alone. SpamTestBuddy can pick out the correct address by applying SkipReceived, a list of networks you define to consider local and ignore. The resulting IP address is conveniently displayed in the new X-SpamTestBuddy header, simplifying your procmail recipes.
Enhancements:
- This is the first public release of this software.
- The configuration file was enhanced for ease of use.
- DNSBL (RBL) support was added.
Download (0.008MB)
Added: 2007-01-16 License: Free To Use But Restricted Price:
1011 downloads
NAT Check 1
Check Your Network Address Translator for Compatibility with Peer-to-Peer Protocols. more>>
Check Your Network Address Translator for Compatibility with Peer-to-Peer Protocols.
If you are accessing the Internet from behind a Network Address Translator (NAT) of some kind, I would appreciate your help in surveying the behavior of different NATs, in terms of how and whether they support a certain technique for enabling peer-to-peer communication between NATted hosts (particularly when both endpoints are behind NATs). Down, you can understand what NAT is.
Suppose there are three communicating hosts: A, B, and C. Host A is a "well-known" Internet server with a permanent IP address, which acts as an "introducer" for the other two nodes. (For example, Host A might be a well-known ultrapeer or a game catalog server of some kind.) Host B, using Host As "introduction" services, would like to establish a direct peer-to-peer connection with host C. Both B and C, however, are behind (probably different) network address/port translators, and neither of them has exclusive use of any public IP address.
To initiate a peer-to-peer connection with host C, host B first sends A a message requesting an "introduction" to host C. A sends B a reply message containing Cs IP address and UDP port number as reported by host C, in addition to Cs IP address and UDP port number as observed by A. (If C is behind a NAT, then these two address/port combinations will be different.) At the same time, host A sends host C a message containing Bs IP address and UDP port numbers - again, both the ones reported by B and the ones observed by A, which will be different if B is behind a NAT.
Now B and C each know that they want to initiate a connection with each other, and they know each others public (NATted) as well as original IP addresses and UDP port numbers. Both B and C now start attempting to send UDP messages directly to each other, at each of the available addresses. If B and C happen to be behind the same NAT, then they will be able to communicate with each other directly using their "originally reported" IP addresses and UDP port numbers.
In the more common case where B and C are behind different NATs, the "originally reported" addresses will be useless because they will both be private IP addresses in different addressing domains. Instead, the IP address/UDP port combinations observed by A can be used in this case to establish direct communication. Although Bs NAT will initially filter out any UDP packets arriving from Cs public (NATted) UDP port directed at Bs public port, the first UDP message B sends to C will cause Bs NAT to open up a new UDP session keyed on Cs public port, allowing future incoming traffic from C to pass through the NAT to B. Similarly, the first few messages from B to C may be filtered out by Cs NAT, but will be able to start passing through the firewall as soon as Cs first message to B causes Cs NAT to open up a new session. In this way, each NAT is tricked into thinking that its respective internal host is the "initiator" of this new session, when in fact the session is fully symmetrical and was initiated (with As help) simultaneously in each direction.
Required NAT Behavior
There is one important requirement that the NATs must satisfy in order for this technique to work: the NATs must be designed so that they assign only one (public IP address, public UDP port) pair to each (internal IP address, internal UDP port) combination, rather than allocating and assigning a new public UDP port for each new UDP session. Recall that a "session" in Internet terminology is defined by the IP addresses and port numbers of both communicating endpoints, so host Bs communication with host A is considered to be one session while host Bs communication with host C is a different session. If Bs NAT, for example, assigns one public UDP port for Bs communication with A, and then assigns B a different public UDP port for the new session B tries to open up with C, then the above technique for peer-to-peer communication will not work because Cs messages to B will be directed to the wrong UDP port.
RFC 3022 explicitly allows and suggests that NATs behave in the former, "desirable" fashion, by maintaining a single (public IP, public port) mapping for a given (internal IP, internal port) combination independent of the number of active sessions involving this mapping. This behavior is not only good for compatibility with UDP applications, but it also helps to conserve the NATs scarce pool of public port numbers. Maintaining a consistent public port mapping does not adversely affect security in any way, either, because incoming traffic can still be filtered on a per-session basis regardless of how addresses are translated. There in fact appears to be no good reason not to implement the desirable behavior in a NAT, except perhaps for the implementation simplicity of naively allocating a new public port for every new session. Unfortunately, RFC 3022 does not require NATs to implement the desirable behavior, which has led me to wonder just how many real NATs actually do, and hence this page.
What NAT Check Does
The program natcheck.c is basically just a program that "pings" a well-known UDP port at two different servers that are publically accessible on the Internet. Both of these servers run the program natserver.c, with the command-line arguments "1" and "2" respectively. In addition, there a third "conspiring" server runs natserver with the command-line argument "3". Whenever each of the first two servers receives a UDP request, it not only sends a reply directly to the sender of that request, but also sends a message to the third server, which in turn "bounces" the reply back to the original client. The effect is that the client will receive not only solicited "ping" replies from the server the request was directed to, but also "unsolicited" replies from the third server.
To determine if the network address translator in use is implementing the desirable behavior of maintaining a single (public IP address, public port) mapping for a given (client IP address, client port), the client program natcheck.c basically just initiates a sequence of simultaneous pings to the first two servers (in case some of the requests or replies are lost in transit) and checks that the clients address and UDP port as reported by both servers is the same. If the NAT naively allocates a new public port for each new session, then the source port as reported by the two servers will be different, and its time to upgrade your NAT.
The replies echoed from the third server are used only to check whether the NAT properly filters out unsolicited incoming traffic on a per-session basis. Since the client never sends any messages to the third server, if the NAT is properly implementing firewall functionality, the client should never see the third servers echoed replies even after opening up active communication sessions with the first two servers.
Enhancements:
- The NAT Check client no longer attempts to guess whether you have Basic NAT or Network Address/Port Translation (NAPT). It turns to be quite difficult to test for this property reliably, because many NAPTs attempt to bind a private UDP port to a public port with the same port number if that port number is available, causing NAT Check to falsely report Basic NAT. The only way to test for this property reliably would be to run NAT Check on at least two client machines simultaneously, and since this property isnt terribly important to P2P apps its just not worth the trouble.
- The NAT Check client now tests for one additional NAT feature, which I call loopback translation. If a NAT supports loopback translation, it means that a host on the private network behind the NAT can communicate with other hosts on the same private network using public (translated) port bindings assigned by the NAT. Most NATs probably do not support this feature yet, but it may become increasingly important in the future where P2P clients may be located behind a common ISP-deployed NAT as well as individual home NATs. More details on loopback translation will appear in the next version of my Internet-Draft, to be released soon.
- The NAT Check client program now has a command-line option, "-v", which turns on verbose messages during the test.
<<lessIf you are accessing the Internet from behind a Network Address Translator (NAT) of some kind, I would appreciate your help in surveying the behavior of different NATs, in terms of how and whether they support a certain technique for enabling peer-to-peer communication between NATted hosts (particularly when both endpoints are behind NATs). Down, you can understand what NAT is.
Suppose there are three communicating hosts: A, B, and C. Host A is a "well-known" Internet server with a permanent IP address, which acts as an "introducer" for the other two nodes. (For example, Host A might be a well-known ultrapeer or a game catalog server of some kind.) Host B, using Host As "introduction" services, would like to establish a direct peer-to-peer connection with host C. Both B and C, however, are behind (probably different) network address/port translators, and neither of them has exclusive use of any public IP address.
To initiate a peer-to-peer connection with host C, host B first sends A a message requesting an "introduction" to host C. A sends B a reply message containing Cs IP address and UDP port number as reported by host C, in addition to Cs IP address and UDP port number as observed by A. (If C is behind a NAT, then these two address/port combinations will be different.) At the same time, host A sends host C a message containing Bs IP address and UDP port numbers - again, both the ones reported by B and the ones observed by A, which will be different if B is behind a NAT.
Now B and C each know that they want to initiate a connection with each other, and they know each others public (NATted) as well as original IP addresses and UDP port numbers. Both B and C now start attempting to send UDP messages directly to each other, at each of the available addresses. If B and C happen to be behind the same NAT, then they will be able to communicate with each other directly using their "originally reported" IP addresses and UDP port numbers.
In the more common case where B and C are behind different NATs, the "originally reported" addresses will be useless because they will both be private IP addresses in different addressing domains. Instead, the IP address/UDP port combinations observed by A can be used in this case to establish direct communication. Although Bs NAT will initially filter out any UDP packets arriving from Cs public (NATted) UDP port directed at Bs public port, the first UDP message B sends to C will cause Bs NAT to open up a new UDP session keyed on Cs public port, allowing future incoming traffic from C to pass through the NAT to B. Similarly, the first few messages from B to C may be filtered out by Cs NAT, but will be able to start passing through the firewall as soon as Cs first message to B causes Cs NAT to open up a new session. In this way, each NAT is tricked into thinking that its respective internal host is the "initiator" of this new session, when in fact the session is fully symmetrical and was initiated (with As help) simultaneously in each direction.
Required NAT Behavior
There is one important requirement that the NATs must satisfy in order for this technique to work: the NATs must be designed so that they assign only one (public IP address, public UDP port) pair to each (internal IP address, internal UDP port) combination, rather than allocating and assigning a new public UDP port for each new UDP session. Recall that a "session" in Internet terminology is defined by the IP addresses and port numbers of both communicating endpoints, so host Bs communication with host A is considered to be one session while host Bs communication with host C is a different session. If Bs NAT, for example, assigns one public UDP port for Bs communication with A, and then assigns B a different public UDP port for the new session B tries to open up with C, then the above technique for peer-to-peer communication will not work because Cs messages to B will be directed to the wrong UDP port.
RFC 3022 explicitly allows and suggests that NATs behave in the former, "desirable" fashion, by maintaining a single (public IP, public port) mapping for a given (internal IP, internal port) combination independent of the number of active sessions involving this mapping. This behavior is not only good for compatibility with UDP applications, but it also helps to conserve the NATs scarce pool of public port numbers. Maintaining a consistent public port mapping does not adversely affect security in any way, either, because incoming traffic can still be filtered on a per-session basis regardless of how addresses are translated. There in fact appears to be no good reason not to implement the desirable behavior in a NAT, except perhaps for the implementation simplicity of naively allocating a new public port for every new session. Unfortunately, RFC 3022 does not require NATs to implement the desirable behavior, which has led me to wonder just how many real NATs actually do, and hence this page.
What NAT Check Does
The program natcheck.c is basically just a program that "pings" a well-known UDP port at two different servers that are publically accessible on the Internet. Both of these servers run the program natserver.c, with the command-line arguments "1" and "2" respectively. In addition, there a third "conspiring" server runs natserver with the command-line argument "3". Whenever each of the first two servers receives a UDP request, it not only sends a reply directly to the sender of that request, but also sends a message to the third server, which in turn "bounces" the reply back to the original client. The effect is that the client will receive not only solicited "ping" replies from the server the request was directed to, but also "unsolicited" replies from the third server.
To determine if the network address translator in use is implementing the desirable behavior of maintaining a single (public IP address, public port) mapping for a given (client IP address, client port), the client program natcheck.c basically just initiates a sequence of simultaneous pings to the first two servers (in case some of the requests or replies are lost in transit) and checks that the clients address and UDP port as reported by both servers is the same. If the NAT naively allocates a new public port for each new session, then the source port as reported by the two servers will be different, and its time to upgrade your NAT.
The replies echoed from the third server are used only to check whether the NAT properly filters out unsolicited incoming traffic on a per-session basis. Since the client never sends any messages to the third server, if the NAT is properly implementing firewall functionality, the client should never see the third servers echoed replies even after opening up active communication sessions with the first two servers.
Enhancements:
- The NAT Check client no longer attempts to guess whether you have Basic NAT or Network Address/Port Translation (NAPT). It turns to be quite difficult to test for this property reliably, because many NAPTs attempt to bind a private UDP port to a public port with the same port number if that port number is available, causing NAT Check to falsely report Basic NAT. The only way to test for this property reliably would be to run NAT Check on at least two client machines simultaneously, and since this property isnt terribly important to P2P apps its just not worth the trouble.
- The NAT Check client now tests for one additional NAT feature, which I call loopback translation. If a NAT supports loopback translation, it means that a host on the private network behind the NAT can communicate with other hosts on the same private network using public (translated) port bindings assigned by the NAT. Most NATs probably do not support this feature yet, but it may become increasingly important in the future where P2P clients may be located behind a common ISP-deployed NAT as well as individual home NATs. More details on loopback translation will appear in the next version of my Internet-Draft, to be released soon.
- The NAT Check client program now has a command-line option, "-v", which turns on verbose messages during the test.
Added: 2006-06-21 License: GPL (GNU General Public License) Price:
737 downloads
Low Resolution Modeline Calculator 0.9.2
Low Resolution Modeline Calculator is a modeline calculator for legacy CRT displays. more>>
Low Resolution Modeline Calculator is a modeline calculator for legacy CRT displays, including TVs, arcade monitors, and VGA monitors.
Low Resolution Modeline Calculator can also be used to calculate low resolution modelines for modern multisync PC monitors.
As its name implies, it is not designed for calculating large resolutions, resolutions that operate over 65kHz.
Options:
-v, --vsync
Calculate the nearest mode in vertical synchronization.
-b, --bestscan
Calculate the nearest best scan mode.
-i, --interlace
Include support for interlaced calculations. Interlaced modes are not supported by many video cards. You should only enable this option if you know your video card supports them.
-d, --doublescan
Include support for doublescanned calculations. Doublescanned modes are not supported by many video cards. You should only enable this option if you know your video card supports them.
-n, --nostretch
Do not stretch modes that are out of range for your monitor. You should use this option if you know that your application does not support integer stretching.
-y, --ystretch
Assume fractional stretching of the y-resolution. You should use this option if you know that your application supports fractional stretching of the y-resolution and you want to stretch an underscanned mode so that it fills the entire screen.
-l, --lowpclock
Many video cards do not reliably support pixel clocks lower than 8mHz. If you know that your video card and its driver support pixel clocks lower than 8mHz, then you should use this option.
-h, --highpclock
Most X11 video card drivers do not support pixel clocks lower than 12mHz. In some cases your video card may not support pixel clocks lower than 12mHz either (rare). If you know that your video card (or your video card driver) does not support pixel clocks lower than 12mHz, then you should use this option.
-3x4
Stretch the horizontal resolution so that the mode has a 3:4 aspect ratio. You can use this option to correctly display vertical resolutions on a horizontal monitor.
-x, --X11R6
Print modeline in X11 format (default).
-f, --fb
Print modeline in fbset format.
-a, --advmame
Print modeline in AdvanceMAME format.
-s, --SDL
Print modeline in X11 format to stdout and print AdvanceMAME X11 configuration to stderr.
-p, --powerstrip
Print modeline in PowerStrip format.
-pal
Calculate modelines for a PAL Television (15.625kHz).
-ntsc
Calculate modelines for a NTSC Television (15.73426kHz).
-cga
Calculate modelines for a standard resolution arcade monitor (15.7500kHz).
-ega
Calculate modelines for a medium resolution arcade monitor (24.960kHz).
-vga
Calculate modelines for a standard VGA monitor (31.500kHz).
-d9200
Calculate modelines for a Wells-Gardner 9200 arcade monitor (15kHz, 25kHz, 31kHz).
-multi
Calculate modelines for a Multisync PC monitor (default)
Enhancements:
- The --reference option works correctly.
- The DOS version compiles with libxml.
<<lessLow Resolution Modeline Calculator can also be used to calculate low resolution modelines for modern multisync PC monitors.
As its name implies, it is not designed for calculating large resolutions, resolutions that operate over 65kHz.
Options:
-v, --vsync
Calculate the nearest mode in vertical synchronization.
-b, --bestscan
Calculate the nearest best scan mode.
-i, --interlace
Include support for interlaced calculations. Interlaced modes are not supported by many video cards. You should only enable this option if you know your video card supports them.
-d, --doublescan
Include support for doublescanned calculations. Doublescanned modes are not supported by many video cards. You should only enable this option if you know your video card supports them.
-n, --nostretch
Do not stretch modes that are out of range for your monitor. You should use this option if you know that your application does not support integer stretching.
-y, --ystretch
Assume fractional stretching of the y-resolution. You should use this option if you know that your application supports fractional stretching of the y-resolution and you want to stretch an underscanned mode so that it fills the entire screen.
-l, --lowpclock
Many video cards do not reliably support pixel clocks lower than 8mHz. If you know that your video card and its driver support pixel clocks lower than 8mHz, then you should use this option.
-h, --highpclock
Most X11 video card drivers do not support pixel clocks lower than 12mHz. In some cases your video card may not support pixel clocks lower than 12mHz either (rare). If you know that your video card (or your video card driver) does not support pixel clocks lower than 12mHz, then you should use this option.
-3x4
Stretch the horizontal resolution so that the mode has a 3:4 aspect ratio. You can use this option to correctly display vertical resolutions on a horizontal monitor.
-x, --X11R6
Print modeline in X11 format (default).
-f, --fb
Print modeline in fbset format.
-a, --advmame
Print modeline in AdvanceMAME format.
-s, --SDL
Print modeline in X11 format to stdout and print AdvanceMAME X11 configuration to stderr.
-p, --powerstrip
Print modeline in PowerStrip format.
-pal
Calculate modelines for a PAL Television (15.625kHz).
-ntsc
Calculate modelines for a NTSC Television (15.73426kHz).
-cga
Calculate modelines for a standard resolution arcade monitor (15.7500kHz).
-ega
Calculate modelines for a medium resolution arcade monitor (24.960kHz).
-vga
Calculate modelines for a standard VGA monitor (31.500kHz).
-d9200
Calculate modelines for a Wells-Gardner 9200 arcade monitor (15kHz, 25kHz, 31kHz).
-multi
Calculate modelines for a Multisync PC monitor (default)
Enhancements:
- The --reference option works correctly.
- The DOS version compiles with libxml.
Download (0.30MB)
Added: 2006-01-01 License: GPL (GNU General Public License) Price:
1395 downloads
Multicasting Master-Slave Network Filesystem 0.8
Multicasting Master-Slave Network Filesystem is a method of distributing an entire filesystem among several machines. more>>
Network technology evolves quickly, but available bandwidths are still not sufficient for fast transfers of big files to a bunch of clients (for example populating operating systems installation images).
This paper describes Multicasting Master-Slave Network Filesystem (mmsnfs) -- a new method of distributing entire filesystem among several client-machines simultaneously and efficiently.
Moreover it provides mechanisms for modifying distibuted filesystem structure reliably and securing it against introducing inconsistencies. It is designed to be used in small networks of similarly-configured machines, for instance university labs or internet cafes.
<<lessThis paper describes Multicasting Master-Slave Network Filesystem (mmsnfs) -- a new method of distributing entire filesystem among several client-machines simultaneously and efficiently.
Moreover it provides mechanisms for modifying distibuted filesystem structure reliably and securing it against introducing inconsistencies. It is designed to be used in small networks of similarly-configured machines, for instance university labs or internet cafes.
Download (0.055MB)
Added: 2005-04-08 License: GPL (GNU General Public License) Price:
1668 downloads
Pathfinder PKI Daemon 0.1.0
Pathfinder PKI Daemon is designed to provide a mechanism for any program to perform RFC3280-compliant path validation... more>>
Pathfinder PKI Daemon is designed to provide a mechanism for any program to perform RFC3280-compliant path validation of X509 certificates, even when some of the intermediate certificates are not present on the local machine. The project will automatically download any such certificates (and their CRLs) from the Internet as needed using the AIA and CRL distribution point extensions of the certificates it is processing.
By default, the Pathfinder daemon listens on the D-Bus system bus for incoming requests. In this way, any project can easily gain the ability to reliably validate the trustworthiness of X509 certificates. For the convenience of those using OpenSSL or NSS (Netscape Security Services), two libraries containing a callback suitable for use with an SSL connection are provided with the main Pathfinder distribution.
If you are looking for a demonstration of Pathfinder, you may be interested in Pathviewer, which provides a graphical view of path validation via a GTK+ interface.
<<lessBy default, the Pathfinder daemon listens on the D-Bus system bus for incoming requests. In this way, any project can easily gain the ability to reliably validate the trustworthiness of X509 certificates. For the convenience of those using OpenSSL or NSS (Netscape Security Services), two libraries containing a callback suitable for use with an SSL connection are provided with the main Pathfinder distribution.
If you are looking for a demonstration of Pathfinder, you may be interested in Pathviewer, which provides a graphical view of path validation via a GTK+ interface.
Download (0.25MB)
Added: 2007-08-07 License: LGPL (GNU Lesser General Public License) Price:
809 downloads
Mantaray 2.0
Mantaray is a fully distributed peer-to-peer serverless communication & messaging solution, 100% pure Java. more>>
MantaRay project is an innovative open-source data messaging project that was designed to address the continuously changing structure of todays IT environments. MantaRay uses a new approach ? peer-to-peer serverless architecture ? that allowed its development team to create a solution that is significantly more powerful and more efficient than traditional systems.
Being lightweight and OS-agnostic, MantaRay is ideal for heterogeneous, distributed, high-traffic environments. It is highly scalable, providing much faster performance than traditional messaging systems, such as buses and brokers. MantaRays serverless design can also help IT organizations dramatically reduce hardware and operational costs.
While traditional messaging systems such as brokers, buses and home-grown solutions were appropriate for monolithic IT environments, MantaRays design takes into account the continuously changing structure of todays IT environments. By using a peer-to-peer serverless architecture, it provides distributed environments with significantly faster performance and a higher level of robustness, as well as a comparatively rapid implementation time.
MantaRays flexible and lightweight design enables it to be embedded at the application level, thus bringing all functionality to the edges and eliminating the problem of having a single point of congestion and failure. The solution brings high reliability, scalability and availability to enterprise-grade messaging, and is capable of supporting multiple components, business partners, and locations.
The open-source, OS-independent, standards-based MantaRay solution combines cutting edge technologies such as XML, enterprise-grade communication services, and Service Oriented Architecture. Building on the MantaRay framework, developers can cost-effectively create real-time data messaging solutions that reliably connect applications and provide guaranteed delivery, security and transactions.
As a Java Messenger Service (JMS) provider, MantaRay is written in 100% pure Java, supports JMS 1.x & RMI APIs, provides TCP, UDP & SSL transports, and integrates with WebLogic & WebSphere. MantaRay features publish/subscribe (topic) and point-to-point (queue) messaging services, automatic discovery, persistent/non-persistent and durable messages, and message filtering using selectors.
Main features:
- Significantly faster messaging transport performance, particularly in high-traffic applications
- Theoretically infinite scalability
- No single point of failure or congestion
- Robust architecture, such that new applications can be added without changes to the other applications
- Support of heterogeneous environments
- Ease of use and fast deployment
- No application modification necessary
- No redesign of network topology required for every change
- Open source costs and low TCO
Enhancements:
- The MantaRay open source license has been changed to MPL instead of GPL
- High availability features have been fully tested and documented
<<lessBeing lightweight and OS-agnostic, MantaRay is ideal for heterogeneous, distributed, high-traffic environments. It is highly scalable, providing much faster performance than traditional messaging systems, such as buses and brokers. MantaRays serverless design can also help IT organizations dramatically reduce hardware and operational costs.
While traditional messaging systems such as brokers, buses and home-grown solutions were appropriate for monolithic IT environments, MantaRays design takes into account the continuously changing structure of todays IT environments. By using a peer-to-peer serverless architecture, it provides distributed environments with significantly faster performance and a higher level of robustness, as well as a comparatively rapid implementation time.
MantaRays flexible and lightweight design enables it to be embedded at the application level, thus bringing all functionality to the edges and eliminating the problem of having a single point of congestion and failure. The solution brings high reliability, scalability and availability to enterprise-grade messaging, and is capable of supporting multiple components, business partners, and locations.
The open-source, OS-independent, standards-based MantaRay solution combines cutting edge technologies such as XML, enterprise-grade communication services, and Service Oriented Architecture. Building on the MantaRay framework, developers can cost-effectively create real-time data messaging solutions that reliably connect applications and provide guaranteed delivery, security and transactions.
As a Java Messenger Service (JMS) provider, MantaRay is written in 100% pure Java, supports JMS 1.x & RMI APIs, provides TCP, UDP & SSL transports, and integrates with WebLogic & WebSphere. MantaRay features publish/subscribe (topic) and point-to-point (queue) messaging services, automatic discovery, persistent/non-persistent and durable messages, and message filtering using selectors.
Main features:
- Significantly faster messaging transport performance, particularly in high-traffic applications
- Theoretically infinite scalability
- No single point of failure or congestion
- Robust architecture, such that new applications can be added without changes to the other applications
- Support of heterogeneous environments
- Ease of use and fast deployment
- No application modification necessary
- No redesign of network topology required for every change
- Open source costs and low TCO
Enhancements:
- The MantaRay open source license has been changed to MPL instead of GPL
- High availability features have been fully tested and documented
Download (2.0MB)
Added: 2006-05-11 License: MPL (Mozilla Public License) Price:
1262 downloads
Tiger Envelopes 0.8.9
Tiger Envelopes is an easy way to get your email privacy back. more>>
Tiger Envelopes is an easy way to get your email privacy back.
With Tiger Envelopes you use email just like you always have with everyone. And, without you doing anything, your messages are private with people who use envelopes.
The mission of Tiger Envelopes is to make private email easy.
Theres a tradeoff between ease of use and security. For too many years some security professionals have said any privacy thats not perfect is worse than worthless. They say it creates a false sense of security.
No one has a false sense of security about envelopes. Theyre made of paper. But we know theyre much more private than messages without envelopes, such as postcards or email.
Tiger gives you envelopes for your email.
Envelopes comes in two versions, Free and Business.
Tiger Free Envelopes is free in both senses, gratis and libre. It is released under the GPL.
Tiger Business Envelopes is commercial. Its based on Tiger Free Envelopes and adds support plus advanced features businesses need. Source code is included for security audits, but its not GPL.
Enhancements:
- Improved imap support for Thunderbird.
- Start Envelopes from the installer during new installations more reliably.
- Change welcome email message to "what to do" message.
- Save options if installer canceled and options changed.
- Shortened the message in the installers final panel.
- Include how to start the control panel on Linux.
- Removed welcome message from control panel.
- Fixed net.n3.nanoxml.StdXMLParser so searches for dtd in jar files when offline.
- Called closeSession() if user, password, or remote host invalid.
- Improved error messages if remote host not found.
- Ignore files starting with . in the notices directory.
- Created ProxyUser class to manage client and remote user data in proxies.
- Removed thirdparty source that we havent customized.
- Added thirdparty/lib directory with unmodified third party jar files.
- Added setChanged() to envelopes.io classes.
- Delete email accounts from options after theyre anonymized.
- Send notice if Tiger account not defined for a POP3 account.
- Send error message to mail client if POP3 command invalid.
- Validate POP3, IMAP, and SMTP commands from mail client.
- Send 252 response code when VRFY requested of SMTP proxy.
- Send 550 response code when EXPN received by SMTP proxy.
<<lessWith Tiger Envelopes you use email just like you always have with everyone. And, without you doing anything, your messages are private with people who use envelopes.
The mission of Tiger Envelopes is to make private email easy.
Theres a tradeoff between ease of use and security. For too many years some security professionals have said any privacy thats not perfect is worse than worthless. They say it creates a false sense of security.
No one has a false sense of security about envelopes. Theyre made of paper. But we know theyre much more private than messages without envelopes, such as postcards or email.
Tiger gives you envelopes for your email.
Envelopes comes in two versions, Free and Business.
Tiger Free Envelopes is free in both senses, gratis and libre. It is released under the GPL.
Tiger Business Envelopes is commercial. Its based on Tiger Free Envelopes and adds support plus advanced features businesses need. Source code is included for security audits, but its not GPL.
Enhancements:
- Improved imap support for Thunderbird.
- Start Envelopes from the installer during new installations more reliably.
- Change welcome email message to "what to do" message.
- Save options if installer canceled and options changed.
- Shortened the message in the installers final panel.
- Include how to start the control panel on Linux.
- Removed welcome message from control panel.
- Fixed net.n3.nanoxml.StdXMLParser so searches for dtd in jar files when offline.
- Called closeSession() if user, password, or remote host invalid.
- Improved error messages if remote host not found.
- Ignore files starting with . in the notices directory.
- Created ProxyUser class to manage client and remote user data in proxies.
- Removed thirdparty source that we havent customized.
- Added thirdparty/lib directory with unmodified third party jar files.
- Added setChanged() to envelopes.io classes.
- Delete email accounts from options after theyre anonymized.
- Send notice if Tiger account not defined for a POP3 account.
- Send error message to mail client if POP3 command invalid.
- Validate POP3, IMAP, and SMTP commands from mail client.
- Send 252 response code when VRFY requested of SMTP proxy.
- Send 550 response code when EXPN received by SMTP proxy.
Download (54MB)
Added: 2007-06-11 License: GPL (GNU General Public License) Price:
914 downloads
Vacation 1.1.8
Vacation is a mail auto-responder (for when you are on vacation and such), written in Perl. more>>
Vacation is a mail auto-responder (for when you are on vacation and such), written in Perl.
Vacation is loosely based on the vacation program by Larry Wall and Tom Christiansen.
I decided to write a new vacation clone since I could not find a version that would work reliably under Red Hat Linux 6.0. I finally found the old Perl version by Larry Wall and Tom Christiansen -- it was the most full-featured, and it almost worked. So, I decided to rewrite it. You may find the original version as "vacation.orig" in this distribution.
Since then, several others have released similar implementations and updates to vacation. While there is no longer a gap to fill, this version still provides a few unique features, flexibility, and portability.
You may also find a simpler auto-responder script in this distribution called mail-responder.pl. This precursor to vacation may be more appropriate at the system level (e.g., called from the aliases file) as compared to vacation which is designed for individual users.
Enhancements:
- Added a Vacation tag to From: addresses
- Added a routine to properly generate date headers (long overdue!) Thanks to Milivoj Ivkovic for the example
- Added a flag to only respond to specified senders Thanks to Jeff Chan for the feature request
- Improved parsing of From: addresses Thanks to Mark Haidl
- Added $RECIPIENT and $SENDER tokens Thanks to Wayne Fathers for the feature request
<<lessVacation is loosely based on the vacation program by Larry Wall and Tom Christiansen.
I decided to write a new vacation clone since I could not find a version that would work reliably under Red Hat Linux 6.0. I finally found the old Perl version by Larry Wall and Tom Christiansen -- it was the most full-featured, and it almost worked. So, I decided to rewrite it. You may find the original version as "vacation.orig" in this distribution.
Since then, several others have released similar implementations and updates to vacation. While there is no longer a gap to fill, this version still provides a few unique features, flexibility, and portability.
You may also find a simpler auto-responder script in this distribution called mail-responder.pl. This precursor to vacation may be more appropriate at the system level (e.g., called from the aliases file) as compared to vacation which is designed for individual users.
Enhancements:
- Added a Vacation tag to From: addresses
- Added a routine to properly generate date headers (long overdue!) Thanks to Milivoj Ivkovic for the example
- Added a flag to only respond to specified senders Thanks to Jeff Chan for the feature request
- Improved parsing of From: addresses Thanks to Mark Haidl
- Added $RECIPIENT and $SENDER tokens Thanks to Wayne Fathers for the feature request
Download (0.037MB)
Added: 2005-12-20 License: Artistic License Price:
1404 downloads
Qtstalker 0.34
tstalker is a user friendly Technical Analysis package for GNU/Linux. more>>
Qtstalker project is a user friendly Technical Analysis package for GNU/Linux. Similar to commercial wares such as Metastock, Supercharts and Tradestation. Keeps to a lean, simple design for speed, portability, and low resource usage. Because it uses a plugin model, Qtstalker can easily be extended.
Qtstalker is 100% free software, distributed under the terms of the GNU GPL. An active development community is continually adding new features. We appreciate your input towards creating a world-class GNU/Linux TA package.
Main features:
- A point-and-click object-oriented graphical user interface.
- Chart plugins include line, bar, candlestick, point and figure, and swing.
- Customizable colors. Logarithmic and linear arithmetic scaling. Scale to screen.
- Indicators plugins include MACD, MAs, Bollinger Bands, RSI, and dozens more.
- Chart drawing objects: trendlines, buy/sell arrows, horizontal and vertical lines, fibonacci retracement lines, text.
- Quote plugins download data from online sources such as Yahoo, CME, NYBOT.
- Data import plugins for plain-text CSV files and MySQL database.
- The "Plugin" architecture for quotes and indicators enables easy future extensibility.
- Daily, weekly and monthly chart compression (intra-day in development)
- Various data classes to support for investment types such as stocks, futures, indices, ratios and spreads.
- A back testing function allowing indicator performance tests using actual trading data.
- A very basic portfolio manager. Good for tracking open positions. (Suggestions welcome.)
- A Scanner that can scan the qtstalker database for charts that meet a user defined criteria.
Enhancements:
- Installing TA-Lib is now a pre-requisite.
- A single-click is now used to select charts.
- The user can run external scripts that can pass data back to ExScript to be plotted.
- "Indicator Summary" shows a table of all values of active indicators for each item in a Group.
- An XML export can be used by other programs and by the ExScript indicator.
- See misc/CUS_examples to get a quick start with custom CUS indicators.
- Automated help documents were added for indicators.
- All the installation paths were changed from /usr/* to /usr/local/*.
- This now runs very reliably on Mac OS X systems.
<<lessQtstalker is 100% free software, distributed under the terms of the GNU GPL. An active development community is continually adding new features. We appreciate your input towards creating a world-class GNU/Linux TA package.
Main features:
- A point-and-click object-oriented graphical user interface.
- Chart plugins include line, bar, candlestick, point and figure, and swing.
- Customizable colors. Logarithmic and linear arithmetic scaling. Scale to screen.
- Indicators plugins include MACD, MAs, Bollinger Bands, RSI, and dozens more.
- Chart drawing objects: trendlines, buy/sell arrows, horizontal and vertical lines, fibonacci retracement lines, text.
- Quote plugins download data from online sources such as Yahoo, CME, NYBOT.
- Data import plugins for plain-text CSV files and MySQL database.
- The "Plugin" architecture for quotes and indicators enables easy future extensibility.
- Daily, weekly and monthly chart compression (intra-day in development)
- Various data classes to support for investment types such as stocks, futures, indices, ratios and spreads.
- A back testing function allowing indicator performance tests using actual trading data.
- A very basic portfolio manager. Good for tracking open positions. (Suggestions welcome.)
- A Scanner that can scan the qtstalker database for charts that meet a user defined criteria.
Enhancements:
- Installing TA-Lib is now a pre-requisite.
- A single-click is now used to select charts.
- The user can run external scripts that can pass data back to ExScript to be plotted.
- "Indicator Summary" shows a table of all values of active indicators for each item in a Group.
- An XML export can be used by other programs and by the ExScript indicator.
- See misc/CUS_examples to get a quick start with custom CUS indicators.
- Automated help documents were added for indicators.
- All the installation paths were changed from /usr/* to /usr/local/*.
- This now runs very reliably on Mac OS X systems.
Download (1.0MB)
Added: 2007-06-18 License: GPL (GNU General Public License) Price:
869 downloads
JGuiGen rev-237
JGuiGen is a Java GUI Generation System Elegant CRUD (Create/Review/Update/Delete). more>>
JGuiGen is a Java GUI Generation System Elegant CRUD (Create/Review/Update/Delete). It supports any major database using JDBC. It generates fully internationalized and accessible screens that allow users to search tables, run reports, and calculate summary stats.
It generates multi-user safe screens with help buttons that work, generates test cases to test the generated GUIs, and generates HTML documentation about the GUIs generated.
Here is a partial list of classes that are included and used by JGuiGen:
- BoundedTextField.java - Creates a JTextField that will not accept more than x characters where you define the x value. BoundedPlainDocument.java - part of BoundedTextField
- CustomViewer.java - This is a pop-up viewer for JTables. It allows you to view the contents of long strings or text fields.
- DateDialog.java - pop-up calendar for choosing a date.
- DoublyLinkedList.java - create two lists, side by side. Move items from side to the other in order to select a group of options, features, tasks, people etc.
- Frequency Count routine - Create a table that shows a count of the values in a column in a result set.
- GeneralDialog.java - a generic three button, give text and ask a question screen.
- GeneralDialog4Btn.java - a generic four button, give text and ask a question screen.
- GetBrowserAndWP.java - code to ask a user for the path to their word processor and Browser. These values are stored in a table and used to call up these applications as needed.
- History.java - code to view an HTML file. The date and time a user views the file is stored and they are only offered the option to view the file when it is newer than the one they last viewed. Used by a developer to notify users of changes in the application they are using.
- JFreeReports example - generate a report using an existing JTable of data.
- JSearchableComboBox.java - A JComboBox with "Look-ahead". It fills in the most probable answer based upon what the user has entered so far. (This fills a much needed void in Java. By default in a pup-up list if your user types FL for Florida they will get Louisiana. It goes to Florida with the F and then Louisiana with the L. The look-ahead system will leave them on Florida.
- JxFrame.java - a class to inherit instead of JFrame. This gives a single point to make modifications that will affect each frame in an entire application. This one adds the automatic determination of Look and Feel code. It also informs the system to make button more active.
- JxButton.java -a class to inherit instead of JButton. This gives a single point to make modifications that will affect each frame in an entire application.
- JxLabel.java - a class to inherit instead of JLabel. This gives a single point to make modifications that will affect each frame in an entire application.
- JxTextArea.java - a class to inherit instead of JTextArea. This gives a single point to make modifications that will affect each frame in an entire application. This one makes the tab key exit a JTextArea that is being edited. The default requires a user to press CTRL-Tab. ListDialog.java - a generic screen to show a list that the user chooses an option from. It has an optional "Add a new value" feature.
- LowVisionMetalLookAndFeel.java - code to change the look and feel to very large text and very high contrast.
- MutableInteger.java - code to pass an integer value into a class and allow changes made in the class to be known by the calling class.
- NumericPlainDocument.java - Part of the Numeric TextField class.
- NumericTextField.java - creates a JTextField that accepts a number with a specified number of decimal places.
- ProgressMonitorDemo.java - and ProgressMonitorInc.java and ProgressMonitorWork.java. I found it very difficult to get the ProgressMonitor (a small pop-up that fills as your long running task runs) to work. I finally figured out something that works reliably and these three classes show how to do it.
- PrintScreen code - this code is included inside the various classes that JGuiGen generates.
- RegexFormatter.java - code to help apply a Regex value to a JFormattedText field
- RowLayout1.java - a layout manager that includes one column of labels and then a variable number of columns. This can be used for most business applications.
- RowLayoutConstraint.java - part of the rowlayout manager.
- SetIcon.java - code to replace the coffee cup icon on each frame.
- SQLWhereClause.java - a class to pop-up a simple SQL Where clause generator. It includes the ability to name, save and rerun queries. It also saves and runs reports using JFreeReports.
- StreamEditorPane.java - Part of the TextEditor class.
- SwitchLF.java - code to switch look and feels in a running application.
- TableMap.java - part of the TableSorter class.
- TableSorter.java - code to make a JTable that sorts on each column when the column header is clicked.
- TernarySearchTree.java - part of the JSearchableComboBox class.
- TextViewer.java - Code to view a Text field.
- TextEditor.java - Code to edit a text field. This includes a way to make Tab exit a JTextArea (which is not the default for Java.)
- TableHeaderJLabel.java - Code to display special headers over a column in a JTable.
- WholeNumberField.java - code to create a JTextField that will only accept integer values.
- Switch Look and Feel menu
- Change Locale menu
- Change Font menu
<<lessIt generates multi-user safe screens with help buttons that work, generates test cases to test the generated GUIs, and generates HTML documentation about the GUIs generated.
Here is a partial list of classes that are included and used by JGuiGen:
- BoundedTextField.java - Creates a JTextField that will not accept more than x characters where you define the x value. BoundedPlainDocument.java - part of BoundedTextField
- CustomViewer.java - This is a pop-up viewer for JTables. It allows you to view the contents of long strings or text fields.
- DateDialog.java - pop-up calendar for choosing a date.
- DoublyLinkedList.java - create two lists, side by side. Move items from side to the other in order to select a group of options, features, tasks, people etc.
- Frequency Count routine - Create a table that shows a count of the values in a column in a result set.
- GeneralDialog.java - a generic three button, give text and ask a question screen.
- GeneralDialog4Btn.java - a generic four button, give text and ask a question screen.
- GetBrowserAndWP.java - code to ask a user for the path to their word processor and Browser. These values are stored in a table and used to call up these applications as needed.
- History.java - code to view an HTML file. The date and time a user views the file is stored and they are only offered the option to view the file when it is newer than the one they last viewed. Used by a developer to notify users of changes in the application they are using.
- JFreeReports example - generate a report using an existing JTable of data.
- JSearchableComboBox.java - A JComboBox with "Look-ahead". It fills in the most probable answer based upon what the user has entered so far. (This fills a much needed void in Java. By default in a pup-up list if your user types FL for Florida they will get Louisiana. It goes to Florida with the F and then Louisiana with the L. The look-ahead system will leave them on Florida.
- JxFrame.java - a class to inherit instead of JFrame. This gives a single point to make modifications that will affect each frame in an entire application. This one adds the automatic determination of Look and Feel code. It also informs the system to make button more active.
- JxButton.java -a class to inherit instead of JButton. This gives a single point to make modifications that will affect each frame in an entire application.
- JxLabel.java - a class to inherit instead of JLabel. This gives a single point to make modifications that will affect each frame in an entire application.
- JxTextArea.java - a class to inherit instead of JTextArea. This gives a single point to make modifications that will affect each frame in an entire application. This one makes the tab key exit a JTextArea that is being edited. The default requires a user to press CTRL-Tab. ListDialog.java - a generic screen to show a list that the user chooses an option from. It has an optional "Add a new value" feature.
- LowVisionMetalLookAndFeel.java - code to change the look and feel to very large text and very high contrast.
- MutableInteger.java - code to pass an integer value into a class and allow changes made in the class to be known by the calling class.
- NumericPlainDocument.java - Part of the Numeric TextField class.
- NumericTextField.java - creates a JTextField that accepts a number with a specified number of decimal places.
- ProgressMonitorDemo.java - and ProgressMonitorInc.java and ProgressMonitorWork.java. I found it very difficult to get the ProgressMonitor (a small pop-up that fills as your long running task runs) to work. I finally figured out something that works reliably and these three classes show how to do it.
- PrintScreen code - this code is included inside the various classes that JGuiGen generates.
- RegexFormatter.java - code to help apply a Regex value to a JFormattedText field
- RowLayout1.java - a layout manager that includes one column of labels and then a variable number of columns. This can be used for most business applications.
- RowLayoutConstraint.java - part of the rowlayout manager.
- SetIcon.java - code to replace the coffee cup icon on each frame.
- SQLWhereClause.java - a class to pop-up a simple SQL Where clause generator. It includes the ability to name, save and rerun queries. It also saves and runs reports using JFreeReports.
- StreamEditorPane.java - Part of the TextEditor class.
- SwitchLF.java - code to switch look and feels in a running application.
- TableMap.java - part of the TableSorter class.
- TableSorter.java - code to make a JTable that sorts on each column when the column header is clicked.
- TernarySearchTree.java - part of the JSearchableComboBox class.
- TextViewer.java - Code to view a Text field.
- TextEditor.java - Code to edit a text field. This includes a way to make Tab exit a JTextArea (which is not the default for Java.)
- TableHeaderJLabel.java - Code to display special headers over a column in a JTable.
- WholeNumberField.java - code to create a JTextField that will only accept integer values.
- Switch Look and Feel menu
- Change Locale menu
- Change Font menu
Download (10.1MB)
Added: 2006-05-22 License: GPL (GNU General Public License) Price:
1256 downloads
Ping Tunnel 0.61
Ping Tunnel is a tool for reliably tunneling TCP connections over ICMP echo request. more>>
Ptunnel is an application that allows you to reliably tunnel TCP connections to a remote host using ICMP echo request and reply packets, commonly known as ping requests and replies. At first glance, this might seem like a rather useless thing to do, but it can actually come in your help in some cases.
Setting: Youre on the go, and stumble across an open wireless network. The network gives you an IP address, but wont let you send TCP or UDP packets out to the rest of the internet, for instance to check your mail. What to do? By chance, you discover that the network will allow you to ping any computer on the rest of the internet. With ptunnel, you can utilize this feature to check your mail, or do other things that require TCP.
Main features:
- Tunnel TCP using ICMP echo request and reply packets
- Connections are reliable (lost packets are resent as necessary)
- Handles multiple connections
- Acceptable bandwidth (150 kb/s downstream and about 50 kb/s upstream are the currently measured maximas for one tunnel, but with tweaking this can be improved further)
- Authentication, to prevent just anyone from using your proxy
<<lessSetting: Youre on the go, and stumble across an open wireless network. The network gives you an IP address, but wont let you send TCP or UDP packets out to the rest of the internet, for instance to check your mail. What to do? By chance, you discover that the network will allow you to ping any computer on the rest of the internet. With ptunnel, you can utilize this feature to check your mail, or do other things that require TCP.
Main features:
- Tunnel TCP using ICMP echo request and reply packets
- Connections are reliable (lost packets are resent as necessary)
- Handles multiple connections
- Acceptable bandwidth (150 kb/s downstream and about 50 kb/s upstream are the currently measured maximas for one tunnel, but with tweaking this can be improved further)
- Authentication, to prevent just anyone from using your proxy
Download (0.047MB)
Added: 2006-07-04 License: BSD License Price:
1234 downloads
KXplayer 0.2 pre1
KXplayer is a very simple media player, based on xine. more>>
KXplayer is a very simple media player, based on xine. Its my hobby-project - just a way to get a better knowledge of KDEs internals.
Besides I wanted to learn programming C++ and since I believe the best way to learn programing is to write a program, I just made my mind to write a multimedia player.
Since it is a player, this word had to be in present in the title. The K and X appered there because of KDE (interface) and XINE (backend).
I took the decision to write a player because I needed one. I needed a good media player for KDE (something like XMMS with KDE inderface), which would be working as reliably as possible.
At present my PC is a 750MHz Duron with 128MB RAM and its almost imposible to work in OpenOffice.org and listen to MP3/OGG at the same time. Running XMMS and OpenOffice 1.x together on my Mandrake results in sound fragmentation.
For some time Ive been using boombox (you can find it in kde-apps). It is based on xine and I found it working better than xmms - almost no fragmentation. Unfortunately boomboxs interface is a bit strange (IMHO) and its not saving the equalizer settings (very annoying).
<<lessBesides I wanted to learn programming C++ and since I believe the best way to learn programing is to write a program, I just made my mind to write a multimedia player.
Since it is a player, this word had to be in present in the title. The K and X appered there because of KDE (interface) and XINE (backend).
I took the decision to write a player because I needed one. I needed a good media player for KDE (something like XMMS with KDE inderface), which would be working as reliably as possible.
At present my PC is a 750MHz Duron with 128MB RAM and its almost imposible to work in OpenOffice.org and listen to MP3/OGG at the same time. Running XMMS and OpenOffice 1.x together on my Mandrake results in sound fragmentation.
For some time Ive been using boombox (you can find it in kde-apps). It is based on xine and I found it working better than xmms - almost no fragmentation. Unfortunately boomboxs interface is a bit strange (IMHO) and its not saving the equalizer settings (very annoying).
Download (0.57MB)
Added: 2005-06-14 License: GPL (GNU General Public License) Price:
1595 downloads
Image::MetaData::JPEG::TagLists 0.15
Image::MetaData::JPEG::TagLists contains a collection of tag tables for JPEG segments. more>>
Image::MetaData::JPEG::TagLists contains a collection of tag tables for JPEG segments. Image::MetaData::JPEG::TagLists is an appendix to the main manual page of the Image::MetaData::JPEG module, which the reader should refer to for further details and the general scope.
Valid tags for Exif APP1 data
The Japan Electronics and Information Technology Industries Association (JEITA) set up a standard for an exchange format for digital still cameras pictures, known as Exif. This standard defines a structure for embedding meta-data in a JPEG picture, to be written in the APP1 segment. The generalities and the reference documents about this structure are introduced in the Structure appendix; this section and its subsections list the valid interoperability record tags as well as their format.
Canonical Exif 2.2 and TIFF 6.0 tags for IFD0 and IFD1
In general, IFD0 and IFD1 can host tags from the same set. These tags are divided in three categories: canonical, additional and registered to companies. The tags listed in the following table are to be considered canonical; they are described at length in the Exif standard document, and can be found both in the IFD0 and in the IFD1 (some of them, in fact, must be present in both directories).
The class column carries the tag class; possible values are: A (image data structure), B (offsets), C (image data characteristics), D (other tags) and P (pointers to other IFDs). The two following columns show tag hexadecimal codes and names. The type column specifies the (always unsigned) tag type: I (short or long), S (short), L (long), R (rational) and A (ASCII, always null terminated). The count column obviously carries the tag count (- for a variable count, either because it is a variable length string or because it depends on other tags).
The IFD0 and IFD1 columns specify the support level in the respective directory; each column comprises four letters, because both the primary image (IFD0) and the thumbnail (IFD1) can come in four varieties (uncompressed chunky, uncompressed planar, uncompressed YCC and JPEG compressed).
This module currently focuses only on JPEG pictures (not TIFF), so only the fourth letter of the IFD0 column is interesting, but note that the thumbnail of a JPEG image can be uncompressed. The support level codes stand for: M (mandatory), R (recommended), O (optional), N (not_recorded) and J (included in JPEG marker and so not recorded).
The thumbnail-only column shows a T for those records which cannot be set/changed by the user exception made during a thumbnail update action (and some of them are calculated automatically anyway). Note that, in some cases, it is possible to set a tag when its support level is N (e.g., the YCbCr stuff in IFD1): picture displaying programs should however simply ignore it. Some other tags, concerning offsets or thumbnail specific information, cannot be set by the module user (they are calculated automatically, more reliably): these are marked by calculated in the notes, or by a T in the thumbnail-only column.
Hexadecimal code count IFD0 IFD1 thumbnail-only
class | Tag name type | supp.supp.| notes
| | | | | | | | |
A 100 ImageWidth I 1 MMMJ MMMJ T (not JPEG) pixels/row
A 101 ImageLength I 1 MMMJ MMMJ T (not JPEG) num. rows
A 102 BitsPerSample S 3 MMMJ MMMJ T (not JPEG) 8,8,8
A 103 Compression S 1 MMMJ MMMM T 1(uncompr.) or 6(JPEG)
A 106 PhotometricInterpretation S 1 MMMN MMMJ 2(RGB) or 6(YCbCr)
D 10e ImageDescription A - RRRR OOOO (see note 1)
D 10f Make A - RRRR OOOO camera manufacturer
D 110 Model A - RRRR OOOO camera model
B 111 StripOffsets I - MMMN MMMN calculated
A 112 Orientation S 1 RRRR OOOO (see note 2)
A 115 SamplesPerPixel S 1 MMMJ MMMJ T (not JPEG) 3 compon.
B 116 RowsPerStrip I 1 MMMN MMMN T (not JPEG)
B 117 StripByteCounts I - MMMN MMMN T (not JPEG)
A 11a XResolution R 1 MMMM MMMM (see note 3)
A 11b YResolution R 1 MMMM MMMM (see note 3)
A 11c PlanarConfiguration S 1 OMOJ OMOJ (see note 4)
A 128 ResolutionUnit S 1 MMMM MMMM (see note 3)
C 12d TransferFunction S 768 RRRR OOOO (see note 5)
D 131 Software A - OOOO OOOO Exif software/firmware
D 132 DateTime A 20 RRRR OOOO (see note 6)
D 13b Artist A - OOOO OOOO owner/photogr./creator
C 13e WhitePoint R 2 OOOO OOOO (see note 5)
C 13f PrimaryChromaticities R 6 OOOO OOOO (see note 5)
B 201 JPEGInterchangeFormat L 1 NNNN NNNM calculated
B 202 JPEGInterchangeFormatLength L 1 NNNN NNNM T (only JPEG)
C 211 YCbCrCoefficients R 3 NNOO NNOO (see note 7)
A 212 YCbCrSubSampling S 2 NNMJ NNMJ (see note 7)
A 213 YCbCrPositioning S 1 NNMM NNOO (see note 7)
C 214 ReferenceBlackWhite R 6 OOOO OOOO (see note 8)
D 8298 Copyright A - OOOO OOOO of photogr./editor
P 8769 ExifOffset L 1 MMMM OOOO calculated
P 8825 GPSInfo L 1 OOOO OOOO calculated
<<lessValid tags for Exif APP1 data
The Japan Electronics and Information Technology Industries Association (JEITA) set up a standard for an exchange format for digital still cameras pictures, known as Exif. This standard defines a structure for embedding meta-data in a JPEG picture, to be written in the APP1 segment. The generalities and the reference documents about this structure are introduced in the Structure appendix; this section and its subsections list the valid interoperability record tags as well as their format.
Canonical Exif 2.2 and TIFF 6.0 tags for IFD0 and IFD1
In general, IFD0 and IFD1 can host tags from the same set. These tags are divided in three categories: canonical, additional and registered to companies. The tags listed in the following table are to be considered canonical; they are described at length in the Exif standard document, and can be found both in the IFD0 and in the IFD1 (some of them, in fact, must be present in both directories).
The class column carries the tag class; possible values are: A (image data structure), B (offsets), C (image data characteristics), D (other tags) and P (pointers to other IFDs). The two following columns show tag hexadecimal codes and names. The type column specifies the (always unsigned) tag type: I (short or long), S (short), L (long), R (rational) and A (ASCII, always null terminated). The count column obviously carries the tag count (- for a variable count, either because it is a variable length string or because it depends on other tags).
The IFD0 and IFD1 columns specify the support level in the respective directory; each column comprises four letters, because both the primary image (IFD0) and the thumbnail (IFD1) can come in four varieties (uncompressed chunky, uncompressed planar, uncompressed YCC and JPEG compressed).
This module currently focuses only on JPEG pictures (not TIFF), so only the fourth letter of the IFD0 column is interesting, but note that the thumbnail of a JPEG image can be uncompressed. The support level codes stand for: M (mandatory), R (recommended), O (optional), N (not_recorded) and J (included in JPEG marker and so not recorded).
The thumbnail-only column shows a T for those records which cannot be set/changed by the user exception made during a thumbnail update action (and some of them are calculated automatically anyway). Note that, in some cases, it is possible to set a tag when its support level is N (e.g., the YCbCr stuff in IFD1): picture displaying programs should however simply ignore it. Some other tags, concerning offsets or thumbnail specific information, cannot be set by the module user (they are calculated automatically, more reliably): these are marked by calculated in the notes, or by a T in the thumbnail-only column.
Hexadecimal code count IFD0 IFD1 thumbnail-only
class | Tag name type | supp.supp.| notes
| | | | | | | | |
A 100 ImageWidth I 1 MMMJ MMMJ T (not JPEG) pixels/row
A 101 ImageLength I 1 MMMJ MMMJ T (not JPEG) num. rows
A 102 BitsPerSample S 3 MMMJ MMMJ T (not JPEG) 8,8,8
A 103 Compression S 1 MMMJ MMMM T 1(uncompr.) or 6(JPEG)
A 106 PhotometricInterpretation S 1 MMMN MMMJ 2(RGB) or 6(YCbCr)
D 10e ImageDescription A - RRRR OOOO (see note 1)
D 10f Make A - RRRR OOOO camera manufacturer
D 110 Model A - RRRR OOOO camera model
B 111 StripOffsets I - MMMN MMMN calculated
A 112 Orientation S 1 RRRR OOOO (see note 2)
A 115 SamplesPerPixel S 1 MMMJ MMMJ T (not JPEG) 3 compon.
B 116 RowsPerStrip I 1 MMMN MMMN T (not JPEG)
B 117 StripByteCounts I - MMMN MMMN T (not JPEG)
A 11a XResolution R 1 MMMM MMMM (see note 3)
A 11b YResolution R 1 MMMM MMMM (see note 3)
A 11c PlanarConfiguration S 1 OMOJ OMOJ (see note 4)
A 128 ResolutionUnit S 1 MMMM MMMM (see note 3)
C 12d TransferFunction S 768 RRRR OOOO (see note 5)
D 131 Software A - OOOO OOOO Exif software/firmware
D 132 DateTime A 20 RRRR OOOO (see note 6)
D 13b Artist A - OOOO OOOO owner/photogr./creator
C 13e WhitePoint R 2 OOOO OOOO (see note 5)
C 13f PrimaryChromaticities R 6 OOOO OOOO (see note 5)
B 201 JPEGInterchangeFormat L 1 NNNN NNNM calculated
B 202 JPEGInterchangeFormatLength L 1 NNNN NNNM T (only JPEG)
C 211 YCbCrCoefficients R 3 NNOO NNOO (see note 7)
A 212 YCbCrSubSampling S 2 NNMJ NNMJ (see note 7)
A 213 YCbCrPositioning S 1 NNMM NNOO (see note 7)
C 214 ReferenceBlackWhite R 6 OOOO OOOO (see note 8)
D 8298 Copyright A - OOOO OOOO of photogr./editor
P 8769 ExifOffset L 1 MMMM OOOO calculated
P 8825 GPSInfo L 1 OOOO OOOO calculated
Download (0.28MB)
Added: 2006-06-15 License: Perl Artistic License Price:
1227 downloads
Klementine 0.18B002
Klementine is a Java program for remote mail retrieval, filtering and forwarding. more>>
Klementine is a Java program for remote mail retrieval, filtering and forwarding. Regular expressions can be applied to the mail header fields and thus characterize the messages as spam or ham.
Identified spam will be deleted directly on the server. Klementine project is most useful for people retrieving their mail through dialup connections.
Main features:
- Input protocols: IMAP, POP3
- Output protocols: STDOUT, SMTP (Port 25)
- Multiple accounts
- Multithreaded account processing
- Fast mail retrieval by strictly separating download and forwarding
- Intelligent rules
- Use of email addresses book from LDAP server as whitelist
- Postpone rule for mails that did not match any rule
- Configuration files may easily be modified by scripts
- Hit statistic report
- Sophisticated logging (through log4j)
Enhancements:
- Fixing a bug that caused the application not to terminate reliably.
<<lessIdentified spam will be deleted directly on the server. Klementine project is most useful for people retrieving their mail through dialup connections.
Main features:
- Input protocols: IMAP, POP3
- Output protocols: STDOUT, SMTP (Port 25)
- Multiple accounts
- Multithreaded account processing
- Fast mail retrieval by strictly separating download and forwarding
- Intelligent rules
- Use of email addresses book from LDAP server as whitelist
- Postpone rule for mails that did not match any rule
- Configuration files may easily be modified by scripts
- Hit statistic report
- Sophisticated logging (through log4j)
Enhancements:
- Fixing a bug that caused the application not to terminate reliably.
Download (2.2MB)
Added: 2006-04-27 License: Artistic License Price:
1277 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above that will reliably search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
