limox, branch session-structThe Linux on mobile XMPP (LimoX) clienthttps://cgit.xengineering.eu/limox/atom?h=session-struct2023-09-04T20:47:31ZAdd xmpp.SessionFrontend.Disconnect()2023-09-04T20:47:31Zxengineeringme@xengineering.eu2023-09-04T20:47:31Zurn:sha1:dc8ff3e7d214c6a390f2aa5c794891b17c418640
This is the first convenience function implemented inside the xmpp
module but for the goroutine of the using application.
xmpp: Add type SessionFrontend2023-09-04T20:44:00Zxengineeringme@xengineering.eu2023-09-04T20:18:53Zurn:sha1:93668403433cbfc22fe9c38ebbd6ef67af625ad2
Some parts of the `xmpp` module functionality should be written for the
using application software. To reference a running session more easily
it is an advantage to have an opaque struct for this instead of
decoupled channels.
Merge branch 'update'2023-09-04T15:28:40Zxengineeringme@xengineering.eu2023-09-04T15:28:40Zurn:sha1:44bc88197196df41ead0ede734295cb2feac066d
This updates from gioui.org v0.1.0 to v0.3.0.
Update to gioui.org v0.3.02023-09-04T15:28:10Zxengineeringme@xengineering.eu2023-09-04T15:28:10Zurn:sha1:8ec8cddbdce0add6c62de0370b32362f7e7bb384Update to gioui.org v0.2.02023-09-04T15:27:12Zxengineeringme@xengineering.eu2023-09-04T15:26:50Zurn:sha1:bd92773ccd795dca6c0613bca3d1fb83b2f25a6dMerge branch 'roster-backend'2023-07-06T19:45:31Zxengineeringme@xengineering.eu2023-07-06T19:45:31Zurn:sha1:16d5f079cc51bffe9f07b356f3a42d5a09a45317
Getting the roster (contact list) is crucial to provide a MVP LimoX
since the chats should be grouped by contacts.
For the MVP it is only relevant to get the roster on connect. Everything
else can be done later.
Apply go fmt2023-07-06T19:43:42Zxengineeringme@xengineering.eu2023-07-06T19:43:42Zurn:sha1:007f413e457ff0b733447acba61b11d6813dd41cImplement roster result handling2023-07-06T19:42:43Zxengineeringme@xengineering.eu2023-07-06T19:42:43Zurn:sha1:a3e01c9a867791b466fe2a3e1d0efd77c840729b
This completes the roster get / result cycle which is needed for a MVP.
Implement roster get request2023-07-06T19:29:34Zxengineeringme@xengineering.eu2023-07-06T19:29:34Zurn:sha1:7960453fb4c56d2fdf9cae08df457027bd62ae6d
This asks the server for the roster / contact list for the current
account.
Use different IQ struct for RX and TX2023-07-06T19:21:33Zxengineeringme@xengineering.eu2023-07-06T19:21:33Zurn:sha1:553537a2c9f08450614648d7184b6bbf212d5ed5
It is quite tricky to write structs with correct XML struct tags which
are suitable for RX and TX because in RX structs all possible fields
have to be addressed and in TX some have to be hidden depending on the
use case.
Migrate bind sending to new generic iq struct2023-07-05T20:34:13Zxengineeringme@xengineering.eu2023-07-05T20:34:13Zurn:sha1:4cc9ea5cd439a1f5306f38838774b46d2b145d9a
This makes the code way less complex.
Migrate bind receive to new iq struct2023-07-05T20:02:02Zxengineeringme@xengineering.eu2023-07-05T20:01:14Zurn:sha1:57845892dbfc6db0648b18e418a6b15218d8526cAdd new generic iq struct2023-07-05T20:01:04Zxengineeringme@xengineering.eu2023-07-05T19:59:37Zurn:sha1:13eeca2177dc767aa7d01c9caed95ae2be736471
This will cover all iq use cases with optional arguments and
sub-elements.
Move bind logic to new xmpp/iq.go2023-07-05T20:01:04Zxengineeringme@xengineering.eu2023-07-05T19:46:12Zurn:sha1:989c6ee9158f67cda2d6287d096c813075d13bd2
The bind request / response works with IQ stanzas. Because of the way
encoding and decoding is done with LimoX / the Go standard library it
makes sense to group IQ-based logic in a separat file since the struct
for IQs will be there.
Merge branch 'msg-backend'2023-07-05T19:26:56Zxengineeringme@xengineering.eu2023-07-05T19:26:56Zurn:sha1:d614346ae08e5384e1dca7306ba64fbdc9931d2e
This adds the XMPP functionality to send and receive XMPP text messages
in one-to-one chats.
Apply go fmt2023-07-05T19:26:12Zxengineeringme@xengineering.eu2023-07-05T19:26:12Zurn:sha1:4dc3723f68c390ed05ddeff13f2378da7ebf2b8fImplement echo bot2023-07-05T19:24:01Zxengineeringme@xengineering.eu2023-07-04T20:51:10Zurn:sha1:ce7814012009ba8f5b72d49e2ec96d5594be895e
This demonstrates the full one-to-one chat message backend without the
need to implement the GUI.
Implement (chat) message receiving backend2023-07-04T20:30:44Zxengineeringme@xengineering.eu2023-07-04T20:30:44Zurn:sha1:107f97f2cd3ff8dbbdb39269e622462c48b0d41c
This sets a handler and the routing up to be able to log chat messages
with body and sender reference.
This can later be used for the GUI.
Merge branch 'element-handling'2023-07-04T20:15:17Zxengineeringme@xengineering.eu2023-07-04T20:10:55Zurn:sha1:48811e7d2487ebc3db49b8af7e20f57db4ac28f4
This moves away from the concept to parse each individual XML token from
the token and group them as a []xml.Token slice for further processing.
While this is still possible, receiving aswell as sending has switched
to define structs with XML tags which can be marshalled and unmarshalled
with the xml.Encoder.EncodeElement() and xml.Decoder.DecodeElement()
functions.
Further documentation can be found at https://pkg.go.dev/encoding/xml#Unmarshal
and https://pkg.go.dev/encoding/xml#Marshal.
This merge reduces with its changes the number of code lines in the XMPP
implementation by around 41 percent!
Apply go fmt2023-07-04T20:09:36Zxengineeringme@xengineering.eu2023-07-04T20:09:36Zurn:sha1:d9fe0a4360770b1e4b6b4fb3686c3275ad1b6e6eRemove unused code2023-07-04T20:09:13Zxengineeringme@xengineering.eu2023-07-04T20:09:13Zurn:sha1:4c9c6c91f9dfca9fd17731d5b0e94aaaace4a137Re-implement resource binding and presence2023-07-04T20:04:05Zxengineeringme@xengineering.eu2023-07-04T20:04:05Zurn:sha1:a23ba089a4e715e68b8c8d4179290692215784a2
This was removed for refactoring.
Add namespace to streamFeatures struct2023-07-04T19:48:23Zxengineeringme@xengineering.eu2023-07-04T19:48:23Zurn:sha1:ed6b4e818f4090c0c707fab49093bc4c3cc3ac20
This prevents collisions.
Re-implement SASL2023-07-04T19:24:04Zxengineeringme@xengineering.eu2023-07-04T19:24:04Zurn:sha1:2c71877e392da6c2691827160142e95142f7bea6
Was broken because of switch to new RX concept.
Introduce handle() as dummy2023-07-04T14:37:27Zxengineeringme@xengineering.eu2023-07-04T14:37:27Zurn:sha1:e529bab2e5df93ff8e9fd415b9d65e9bb6d17695Implement XML element parsing with Generic2023-07-04T14:26:04Zxengineeringme@xengineering.eu2023-07-04T14:26:04Zurn:sha1:7902764e053eb3b8b4d46f8d9caf47d2d5cddd7c
This helps to avoid duplicated code when new XML elements are described
as custom structs.
Rework routing completely2023-07-04T12:26:01Zxengineeringme@xengineering.eu2023-07-04T12:25:21Zurn:sha1:3a5e9fce02264eeed884b15781593479fda9296aFurther reduce complexity of streamFeatures struct2023-07-04T12:06:36Zxengineeringme@xengineering.eu2023-07-04T12:06:36Zurn:sha1:1d3dfa5b93000bc4109ba49ea018e72fbf4f5753Just pass parsed data if successful2023-07-04T12:01:51Zxengineeringme@xengineering.eu2023-07-04T12:01:51Zurn:sha1:3826f3ee7850590142fe51747447dffece332762Reduce complexity of streamFeatures struct2023-07-04T11:57:26Zxengineeringme@xengineering.eu2023-07-04T11:57:26Zurn:sha1:e5257c8a9c3dfcda52fb96fcac2ac81aefb52e55