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.
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 store...
Коментарі
Дописати коментар