Activity for Christian Ferrari
-
Christian Ferrari committed [033987] on Git
Intermediate commit for MySQL and MariaDB, still under debugging
-
Intermediate commit with MariaDB adaptations, but still not stable
-
Intermediate commit for issue #20, ok for MySQL, not ok for MariaDB
-
function lixa_my_retrieve_subtype() completed
-
test commit from ubuntu 16.04
-
intermediate commit
-
Changes for issues #24, #25, #26
-
Small changes related to issue #18, issue #22, and issue #23
-
Fix of issue #19
-
Fix of issue #16
-
Minor doc fix
-
Release 1.7.2 with issues #31 and #32 fixes
-
Fixed the issue related to PHP 8 and SWIG 4.1.0, fixed an issue related to Python in configure.ac
-
PHP wrapper does not work on Debian 12
-
Version that compiles on debian 12.5 32bit and passes the tests without php, perl, python and java API
-
Intermediate commit to emulate issue #32 using Debian 12.5 for 32 bit instead of 32bit arm6
-
Intermediate commit to debug issue #31
-
Version 1.7.1
-
Copyright update for year 2024
-
Fix to second part of https://github.com/tiian/flom/issues/30
-
Fix to first part of https://github.com/tiian/flom/issues/30
-
Version 1.7.0
-
Added test cases for VFS
-
VFS and FUSE source code clean up
-
Removed deprecated functions that were used with very old GLib versions, prior to Ubuntu 14.04
-
Incubating resources now appear and disappear from incubator VFS dir
-
Added incubator dir and files in VFS
-
Starting to implement observability of connection incubator
-
Code clean-up
-
Observability improvement: added file for timestamp_value
-
Improved the observability for sequence resources, sequence_value is now created even after enqueing
-
Added additional info in VFS
-
Added lock_mode file in VFS
-
Implemented the move from waitings to holders
-
Added (TCP) peer_name info in VFS holders subdir when a connection get an immediate lock
-
Fixed possible mutex issue related to possible multiple g_mutex_unlock; signature of inmsg callback function expanded to deal with locker uid
-
Added dirs holders and waitings to VFS, added uid (human readable) to connections
-
Removed memory leak in VFS unmounting, improved VFS thread termination
-
Now it compiles and seems to work even with FUSE3
-
First demo version
-
adding files to dir
-
Mount point for VFS is now linked to command line args and config file
-
Added config parameters for VFS mount point
-
The VFS is now able to expose the content of an N-ary tree defined in memory, at least for directories
-
Commit before removing ino field from flom_vfs_ram_node_t
-
Added first dir levels
-
Mapping uid inode completed for lockers dirs and files
-
VFS inode mapping for top level dirs
-
Implementing uid_to_inode and inode_to_uid mapping functions
-
Added uid (unique identifier) concept, now every locker has its own uid that will be used in the VFS structure
-
This commit incorporates libfuse/examples/hello_ll into FLoM daemon. Apparently there are not conflicts, but the unmount of the FUSE filesystem could be a weak point
-
Added configure.ac stuff to use libfuse
-
Added configure option --disable-testcases
-
Added --disable-testcases to configure script
-
-
Commit for release 1.6.0 - see ChangeLog
-
Updated copyright date
-
Fixed README as suggested https://github.com/tiian/flom/issues/20#issuecomment-1407394085
-
Version 1.9.5 commit, only minor documentation refinement
-
Just to keep CodeQL active
-
You must pay attention to the following aspects: XTA has currently been tested only for MySQL/MariaDB, PostgreSQL, Oracle DB as documented here https://www.tiian.org/lixa/manuals/html/ch08.html#XTA_Technology_Matrix If you want to use DB2 and MQ with XTA, you should use the xta::NativeXaResource as in the below code snippet: xar = new xta::NativeXaResource( "OracleIC_stareg", "/opt/lixa/lib/switch_oracle_stareg.so", "ORACLE_XA+Acc=P/hr/hr+SesTm=30+LogDir=/tmp+" "threads=true+DbgFl=7+SqlNet=lixa_ora_db+"...
-
Hi!What API are you using to develop your application: the TX Transaction Demarcation specification or XTA? Il venerdì 21 gennaio 2022, 04:37:12 CET, NeXgeN <shri2009@users.sourceforge.net> ha scritto: Hi Team We don't have requirement for using mysql . we are testing LIXA as XA transaction manager for DB2 , Postgres and IBM MQ for C++ application . But we cant move past the installation of LIXA 1.9.4 configure. we keep getting following error on our Linux RHEL 7.9 OS configure: error: XTA for C++...
-
Porting LIXA client would be of course easier than porting the LIXA state server; frankly speaking I would not advise the second option because the LIXA state server contains specific Linux related IO optimizations. LIXA client is mostly covered by the POSIX standard + GNU GLIB: I have no idea how far is MSYS from the POSIX standard and GNU GLIB. An interesting aspect to consider is "how many XA Resource Manager client libraries" are available/supported in the MSYS environment? Without those libraries...
-
Typo documentation fix
-
Just to keep CodeQL active
-
Just to keep CodeQL active
-
Dummy commit to keep CodeQL alive
-
Dummy commit to keep CodeQL alive
-
Just to keep CodeQL active
-
Updated copyright years
-
Trying to fix issue 20
-
Updated copyright
-
Trying to fix CodeQL build bug
-
Added documentation for XA functions call order with TX and XTA API
-
Mutual Authentication
-
Channel Encryption
-
Security
-
Release 1.5.22
-
Updated images related to security
-
Updated TLS related documentation
-
Fixed test case for --ignore-signal in Ubuntu 20.04
-
Fix for bug #19
-
Fixed a bug in Makefile that crated a wrong tarball
-
Fix for docker containers lixa/xta-jdk*
-
Commit for release 1.9.4
-
Commit for release 1.9.3
-
Passed tests for Ubuntu 20.04, traditional state engine
-
Added info to use MySQL 8.0
-
Adding support for mariadb-java-client-2.5.3.jar
-
Fixing timing in case0035 to reproduce a specific behavior
-
CentOS 8 passed all tests!
-
Progressing with test case fixing
-
Added CodeQL security scanner configuration
-
Fixing CodeQL automation
-
Added java pre-requisites
-
Merge branch 'master' of github.com:tiian/lixa
-
Fixind security CodeQL security alerts
-
Fixing CodeQL automation
-
Fixing CodeQL automation
-
Fixing CodeQL automation
1 >
Gen AI apps are built with MongoDB Atlas
Atlas offers built-in vector search and global availability across 125+ regions. Start building AI apps faster, all in one place.
Try Free →