| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Finally, the Item has the ability to be displayed on the Form. However, the Client now also requires to keep a list of the active Subscriptions and verify each incoming Item against it, which means that a method of subscribing to subscriptions must be implemented before further testing.
|
| |
|
|
| |
Moved required classpath JARs into a SVN controlled folder so that they are available to anyone who wishes to help develop InstaDisc. Note that the Appframework and Spring-worker JARs were not encapsulated. If you wish to help develop InstaDisc, you'd best be off using NetBeans.
|
| |
|
|
| |
Because of the lack of SQLite Java wrappers, InstaDisc instead uses a BDB database.
|
| |
|
|
| |
After recieving an Item, InstaDisc Client now checks the item for a status of being Well-Formed, as in, it has all of the required headers, the category exists, the category's required semantics are present and the verification is valid.
|
| |
|
|
| |
The Client now listens for connections on port 4444, allowing multiple connections at once. Once a connection iis found, the Cliet waits until the connecton is broken, then downloads the sent dat, parses it into headers and passes it to the Item class.
|
| |
|
