Перейти до основного вмісту

IPC idea

 Is SOAP considered a viable comms method for local processes as an
> alternative to D-BUS, DCOP, etc? I am worried that it's just to slow and
> if I commit to using it that in the future I will realise it doesn't scale
> up.

How can we answer that when we don't know how fast you need it to be? KDE
tried using CORBA for IPC, and that was too slow. SOAP is much slower than
CORBA (at least with good ORBs). But whether it's too slow or not is
impossible to say.

If you're worried, apply a strategy pattern with a factory class and make it
easy for you to switch to another IPC layer later.

Коментарі

Популярні дописи з цього блогу

Home assistant - modbus - HHC-N8I8OP

Thanks to https://www.cncwiki.org/index.php?title=HHC-N8I8OP  I managed to connect this buggy module to home assistant using modbus integration: It is important to have verify delay big to not break logic.  modbus:   - type: tcp     host: 192.168.222.222     port: 5000     name: "modbus1"     switches:       - name: "hhc_r8"         address: 16         write_type: coil         verify:           delay: 36       - name: "hhc_r7"         address: 17         write_type: coil         verify:           delay: 37       - name: "hhc_r6"         address: 18         write_type: coil         verify:           delay: 39       - name: "hhc_r5"         address: 19         write_type: coil         verify:           delay: 48       - name: "hhc_r4"         address: 20         write_type: coil         verify:           delay: 28       - name: "hhc_r3"         address: 21         write_type: coil         verify:           delay: 33

How to symbolicate crash logs in XCode organizer

If you have application distributed through Apple appstore or Testflight you should be able to get automatic crash reports by opening XCode/Window/Organizer menu, then select app and go to Crashes tab. If crashes are not symbolicated you can symbolicate them manually by: 1. In organizer, call for context menu by pressing on crash log call stack section 2. Select "show in finder ..." menu item 3. Navigate up to ~/Library/Developer/Xcode/Products/ [app bundle id]/ [app version]/Crashes/Appstore/ 4. Copy debug symbols there: 5. Go back to Organizer and select "Resymbolicate" context menu item on call stack area. Now you should be able to see symbolicated log. Works for me on XCode 10 and Testflight.

ebusd and vailant ecotech plus plus controller

 ebusctl   localhost: find -c bai bai AccessoriesOne = no data stored bai AccessoriesTwo = no data stored bai ACRoomthermostat = no data stored bai AntiCondensValue = no data stored bai averageIgnitiontime = no data stored bai BlockTimeHcMax = no data stored bai BoilerType = no data stored bai ChangesDSN = no data stored bai CirPump = no data stored bai CodingResistor = no data stored bai CounterStartattempts1 = no data stored bai CounterStartattempts2 = no data stored bai CounterStartAttempts3 = no data stored bai CounterStartAttempts4 = no data stored bai currenterror = no data stored bai DateTime = no data stored bai dcfState = no data stored bai DCFTimeDate = no data stored bai DCRoomthermostat = on bai DeactivationsIFC = no data stored bai DeactivationsTemplimiter = no data stored bai DeltaFlowReturnMax = no data stored bai DisplayMode = no data stored bai DSN = no data stored bai DSNOffset = no data stored bai DSNStart = no data stored bai EBusHeatcontrol = no data stored bai Ebu