Swiftpack.co - Swift Packages by Balancingrock

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Swiftfire -and all its supporting packages- have been issued in their release 1.0.0 SwifterSockets has undergone some file-renaming and some reorganization. Otherwise the functionality itself is unchanged. Switched to Swift Package Manager 4 Minor adjustments for Swift 4. BRUtils was updated to 0.10.0 BRUtils was updated to 0.9.0. The BRUtils package has been upgraded to 0.5.0. In 'SwifterSockets.Connection.swift' the methods incrementUsageCount and decrementUsageCount have been made public. (To help in supporting very large HTTP bodies by Swiftfire). Two bugs were fixed: - A crash that would occur when a connection object received data just (milli seconds) before it was closed. - A bug that would cause connection objects to go missing when a connection was accepted, but no data was ever received. This was a fairly common occurrence and would result in a non-response server. Unfortunately this necessitated the change of 1 interface in Connection.swift: 'receiverData' is now supplanted by 'processReceivedData'. Bugfixes: - Updated references captured by closures - In 'transmitterClosed' the interface is immediately nilled to prevent SSL errors on closing - Added closing of the socket on 'transmitterClosed' Added functionality: - Sorting of connections in the connection pool API changes: - Renamed 'abortConnection' to 'connectionWasClosed' Added "affectInactivityDetection" parameters to Connection - transfer functions. This allows the transmission of data in the inactivity detection action itself. The parameter is by default set to "true" so no code updates are necessary. The sQueue in SwifterSockets.Connection could be deallocated before its processes were finished.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Swiftfire -and all its supporting packages- have been issued in their release 1.0.0 VJson has not undergone any code changes since the previous release. Added tests for undo/redo. Fixed bug on undo/redo for ARRAY and OBJECT with children introduced in 0.15.3 A bug was introduced in 0.15.3 on undo/redo of type changes. This release aims to fix that. This is a maintenance update. The undo/redo mechanism has been reimplemented, it is now object based rather than path based. The file UndoRedo.swift has been removed. The 'location' operation now has an optional 'source' parameter. There have been no error reports for 0.15.2, so updating to 0.15.3 is probably not necessary. The reimplementation of the undo/redo mechanism was done to better support another project of ours. Additions: - Added an operation items:at to extract a number of JSON items from the JSON hierarchy. Changes: - Made the error closure optional for the parse functions. - Updated dependencies. Fixed a problem that could cause a crash when parsing files containing only whitespaces. This is a source breaking change for clarity. Common operations on subitems of ARRAYs and OBJECTs are now called Child operations. Thus there are three different types of operations, best illustrated by the remove operation: ARRAY: remove:at OBJECT: removeItems:forName Common: removeChild, removeChildren:equalTo I.e. the name now clarifies just how the operation should be regarded. Child operations are hierarchy operations that are (in theory) independent of the containers the subitems are in. Als the operation index:ofChildrenEqualTo has been removed as it is too high level for a basic API. The source code (in Array.swift) is still present to aid clients in implementing this client side. The ability to parse and codify top level items (including non-objects) has been expanded to include named items. Some related bugs were fixed. Most notably this means that the parse functions now return an optional! __This will break existing code__. However fixing this should be easy. Changes/Updates: - Added name to top level item (if the top level item has a name) - Fixed error when reading top level string value - Added reading of named top level values - Added return of nil when parsing empty data or only whitespace data - Updated several documentation texts Fixed the error message when parsing illegal null value's. The previous bug -once fixed- unearthed another -even bigger- bug. Its fixed now, but it will have effectively made releases 0.13.0 and 0.13.1 unusable. So please make sure to upgrade to the latest. (0.13.2)

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Release 1.3.0 introduced a commenting system and was a pretty big change overall. Aside from the comment system it also introduced the possibility to have multiple instances of Swiftfire running in parallel. This is very convenient if you run Swiftfire on a development machine. Our website at http://swiftfire.nl is still being updated to detail this release. Since then 1.3.1 and 1.3.2 have removed a few bugs that had crept in up to release 1.3.2. Now 1.3.3 has been released which also completes the addition of the Linux platform for development and deployment. However we ourselves do not use the Linux platform for development (or deployment) thus we depend on you to report any issue's that you might have. Release 1.2.1 adds the sources for the server admin account, adds additional logging when server parameters are changed, and no longer needs explicit saving of changes in server parameters. ## Fixed Issues: - Fixed a bug that prevented updating the server admin root directory - Fixed a bug that prevented a full build after cleaning the build directory ## New features: - No longer needs saving of changes made by the admin - Full logging of all changes made by the server admin - No longer uses the library Html ## Recommendation - Update when convenient. ## User Manual updates: 1. When the server admin website must be changed it will be necessary to install the [Jekyll](https://jekyllrb.com/) static site generator and the [Classic-Jekyll-Theme](https://balancingrock.github.io/classic-jekyll-theme/index.html). 1. The location of the sfadmin website has changed. It is no longer located in `<Project>/sfadmin` but has mbeen moved to `<Project>/sfadmin/_site`. When accessing the serveradmin account for the first time, it will be necessary to update this location. ## Open issues - None ## Anticipated changes - Implement services and functions to allow a blogging site to accept user reactions. No release is envisioned for these changes ## Other Link to previous release: [1.2.0](http://swiftfire.nl/release/2019/09/09/release-1-2-0.html) Release 1.1.0 fixes the most annoying bugs in the earlier release: Fixed Issues: - 1: Domain service names table not properly initialized - 2: Server blacklist should use serverAdminDomain blacklist - 3: List of domains and aliases is not reconstructed correctly from file - 4: Domain services not rebuild before starting server for first time - 5: PHP Settings missing from domain parameters - 6: Domain parameter phpPath is not updated correctly New features: - None Recommendation: Update asap. Swiftfire -and all its supporting packages- have been issued in their release 1.0.0 Swiftfire has gained some functionality since the previous releases, most notably the capability to serve PHP based websites and the preparation of the split in server and domain responsibilities. I.e. server admin and domain admin. This last part is visible in the partly redesigned admin interface. In addition it is now easier to build the project as all the necessary sources are located on github, including the compiled version of OpenSSL. While this is very convenient to gain some quick appreciation of Swiftfire, it should be warned against using any precompiled OpenSSL binary. When you go operational using Swiftfire, you should compile your own version of OpenSSL from the original sources (be aware that some glue code is necessary) The app compiles and runs again, but has not been tested. Also note that the feature set is changing. The last stable release is 0.10.11 This release is for internal purposes only, do not use this code base, use release 0.10.11 or wait until the next release. Fixed a bug on processing a URL with a '&' in it (caused a 'hanger') Fixed missing header logging Upgraded (rename) SwifterJSON to VJson In this release the serveradmin interface was improved on the code generation side of things. A.o. an HTML subproject was introduced to do the HTML code generation. As of this release, Swiftfire now supports very large HTTP request bodies. Previously this was limited to about 32KB, now the size is nearly unlimited. A new service was introduced to enforce completeness of HTTP requests for the traditional 'static websites'. If websites want to make use of very large HTTP bodies, they will need to implement a service specifically for that purpose. As of this release, the SwiftfireCore and SwifterfireConsole have been discontinued. Swiftfire now has a build-in administration site that can be reached under "(any-domain)/serveradmin". The id/password must be set during the initial deployment of the server. In addition a new (sub)project 'Html' has been added to create HTML code. Inspired by the mailing list "swift-sever-dev" (See https://swift.org/community/#mailing-lists) the next release (0.10.10) will offer support for (very) large HTTP request bodies. Support was added for (user) accounts. A web based interface was added for the server admin. The webinterface is not yet complete - and still a bit 'rough', but it allows a server admin to administer the Swiftfire server. This release is a bit 'in-between' as the SwiftfireConsole is also still supported. That will be discontinued in the next release though. When Swiftfire is started for the first time, it is mandatory to create an admin account and to specify the root location of the website that holds the 'sfadmin' pages. The 'sfadmin' website is part of the github distribution, but should probably be copied by the admin to a proper location. To do so, start up the server and browse to 'localhost:6678'. The setup process will then automatically start. Afterwards the server admin can always be reached by browsing to any domain and appending '/serveradmin'.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. With release 2.2.3 SwifterLog can be used on Linux and iOS. Just add SwifterLog as a dependency to your iOS project (in XCode 11 and later). Note that the OSLog target only works on iOS 10 and later. Swiftfire -and all its supporting packages- have been issued in their release 1.0.0 SwifterLog has been upped to version 2.0.0 since it already was above 1.0.0. A minor change has been made to allow ignoring the `type` parameter, or giving it a different default value. With this release support for ASL has been dropped in favor of OSLog. As of MacOS 10.12 Apple has moved away from ASL and pushes for support of OSLog. In addition, Swift 4 made it possible to omit the source specification from the calls by using default values for file, function and line numbers. The API has been simplified to support this. Furthermore, in order to make the API more universal, the optionality of the 'id' and 'type' parameter was dropped. They were replaced by default values of -1 resp 'noType'. Lastly, Swift 4 seems to have changed the implementation of Any which caused a bug when logging messages (strangely enough not always, but sometimes). The 'message' parameter was thus changed from 'Any' to 'CustomStringConvertible' (which actually makes more sense anyway). Switched to Swift Package Manager 4 Minor updates for Swift 4 migration. Updated the included user manual. Due to updates in BRUtils, both SwifterSockets and VJson had to be updated. Release for development purposes. In planning SwifterLog's future, we wanted to add more functionality and allow for more customisation. This meant that we had to sacrifice full backward compatibility. (We tried, but it just leaves too many pitfall possibilities open). Hence we decided to update the current version of SwifterLog to version 1.0.0 so that the upgrade to version 2.0.0 is a clear sign that user source code level changes are necessary. Version 1.0.0 is identical to the previous version, no changes have been made (but for the README file). From now on version 1.0.0 will be updated for reported bugfixes only. Preview for version 2.0.0: - Easier customization (by splitting the project into multiple files, introducing protocols) - Allow for filtering of sources - Allow custom targets - Allow custom formatters for logline output - Easy to create multiple 'loggers' inside a single project Version 2.0.0 is under active development and should be available soon. The SwifterJSON project was renamed to VJson. SwifterSockets was updated to 0.10.8 SwifterJSON was updated to 0.10.6 Both updates are due to increased functionality of BRUtils and SwifterSockets. No bugfixes, manifest update only.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Swiftfire -and all its supporting packages- have been issued in their release 1.0.0 SecureSockets has undergone some file-renaming and some reorganization. Otherwise the functionality itself is unchanged. Switched to Swift Package Manager 4 Minor changes to accommodate Swift 4 and OpenSSL 1.1.0h BRUtils was updated to 0.10.0 which cause SwifterSockets to update to 0.10.10. Updated SwifterSockets to 0.10.9 SwifterSockets was upgraded from 0.10.7 to 0.10.8 (due to additional Swiftfire support requirements, no bugfixes) SwifterSockets was updated to version 0.10.8 (containing 2 bugfixes). Updated SwifterSockets to 0.10.6 Minor bugfix: Added closing of socket when transmitter is closed externally. Updated the manifest file for SwifterSockets 0.10.5 Updated manifest for SwifterSockets 0.10.4.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Switched to Swift Package Manager 4

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Swiftfire -and all its supporting packages- have been issued in their release 1.0.0 KeyedChache has a minor change to reflect the changes in BRUtils. Switched to Swift Package Manager 4 BRUtils was updated to 0.10.0 BRUtils was updated to 0.9.0 Upgraded BRUtils from 0.4.0 to 0.5.0 BRUtils was upgraded to 0.4.0. Upping BRUtils to 0.3.0 Initial release.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Swiftfire -and all packages that it needs- have been issued in their release 1.0.0. BRUtils has been scrubbed for unused code, and existing code was partly renamed in order to create a uniform appearance. Switched to Swift Package Manager 4 Some code was rewritten to allow for considerable complication speed improvements. The migration to Swift 4 uncovered a bug in RawBytes.removeFirstCString. This bug was fixed. No other changes were necessary. Adds CRC32 calculation to the Swift Data type. Added the endianness type with cases 'little' and 'big'. Added machineEndianness global constant. Added crc16 calculation to Data. Added typed extraction of basic types from an UnsafeRawPointer. Added the RawBytes protocol to allow easy encoding/decoding into a foundation Data object. Intended use: var data = Data() let f = Float(1.56e-8) data.append(f) // To encode guard let ff = data.removeFirstFloat() else { print("not enough bytes") } // to decode It almost goes without saying that the sequence of encoding & decoding should be the same. The standard library can have some unexpected behaviours when converting units between types. For example, converting an Int32 to an Int8 can fail, but and Int8 from an NSNumber made from an In32 will not fail. To add consistency for type conversion, a series of 'clamped' factories has been added to many base types. For example: let i32: Int32 = 46788 let i8 = Int8.clamped(i32) will produce the value Int8.max for the i8 parameter. Just as let i8 = Int8.clamped(NSNumber(value: 1e20)) will do. Across all clamped conversions the new value will either have the same value as the originating number or it will be limited against either end, its max or min value. Clamped functions have been added to: Int, UInt, Int8, UInt8, Int16, UInt16, Int32, UInt32, Int64, UInt64, and Float. Added new file: TimeRelated.swift Added extensions: 1 Array - range: Returns the a range from startIndex to endIndex - clamp: Clamps ensures that the value of an index is not outside the range startIndex ... endIndex 2 timespec - init(TimeInterval) 3 timeval - init(TimeInterval) 4 TimeInterval - init(timespec) - init(timeval) Added new function: - public sleep(TimeInterval) -> TimeInterval Allows sub-second resolution for the sleep. Added extension to convert to/from TimeInterval, timespec and timeval. Added wrapper for nanosleep.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Swiftfire -and all its supporting packages- have been issued in their release 1.0.0 Http has not been updated for this release. Switched to Swift Package Manager 4 Documentation and code streamlining. Improved the constructor to increase the fit with Swiftfire Renamed (Http) Operator to (Http) Method