#foswiki 2016-10-03,Mon

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***gac410 has left [03:50]
......................................... (idle for 3h20mn)
ChanServ sets mode: +o CDot [07:10]
............ (idle for 56mn)
FoswikiOnSlack3<nuddlegg> Holidays in Germany [08:06]
................ (idle for 1h15mn)
***tuor has quit IRC (Quit: WeeChat 1.5) [09:21]
................................... (idle for 2h50mn)
ChanServ sets mode: +o gac410
gac410 sets mode: +v FoswikiBot
gac410 sets mode: +v WikiRingBot
[12:11]
......... (idle for 42mn)
gac410Hi all ... Don't forget - release meeting - 5 minutes - #foswiki-release [12:55]
................... (idle for 1h30mn)
vrurgjomo: here yet? [14:25]
jomoyet - still :) [14:26]
vrurgI'm back to the clusterisation thing. Foswiki isn't scalable now. It is limited with capabilities of a single server. Would we ever want to get beyond this limitation there must be DB store and DB LSC.
These are the two blocking entities.
[14:27]
jomonot really DB - but network accessible config (any) . DB is one of such network accesible datastore..
for the clustering you could have alone REST server for such purpose..
[14:29]
vrurgBut the most commonly used. Otherwise – yes. [14:29]
jomothe point is - it must be network accessible [14:30]
vrurgREST for serving LSC? What about the storage? [14:30]
jomomean Foswiki::Store? (or the storage-format (for LSC)? [14:30]
FoswikiBothttps://trunk.foswiki.org/System/PerlDoc?module=Foswiki::Store [14:31]
vrurgFoswiki::Store. [14:31]
jomoone of the main problems of teh Foswiki (also it's strength) - it tries solving everything. Good for endusers, but very BAD for the developers - no clear separation. [14:32]
vrurgAnyway, I hope to get my new extensions accepted. If they're the ability to inherit and replace core classes would let extension developers implement anything – the limits are only one's imagination. [14:32]
jomoHave the whole Store as an network-server alone - VERY GOOD IDEA
and it is already invented - it is called a CMIS :)
[14:32]
vrurgYou talk about micro-services here. Yes, good thing. [14:33]
jomobreak foswiki to SMALLER parts - for this monolithic design you will hardly find other helper-develoepr for your way-of-the-hero :( [14:34]
vrurgWith pure OO and inter-object communication being done using method calls only it's even possible to rewrite the method calling so that it ends up with an RPC call. So, an object actually be located anywhere. [14:36]
jomoconfigure-subsystem should be universal. Not only foswiki specific. But that also means - we could DELIMIT the whole config from the "core" as one alone subsystem. The same applies for the "web-framework" part. It should have nothing with the "core of the foswiki" - witch is (simplyfied): just an templating engine, which could exapnd user-defined macros and renders wiki-text".... [14:37]
vrurgBut it's a big-big job. And it's to be carefully considered too because I once read an article where developers complained that moving back away from microservice actually gave them some increase in productivity.
Ok, now it's my time to leave for some time. Be back in ~2hrs, perhaps.
[14:37]
jomoyeah - can't be done by the "start hacking" method. The good microservice "network" is based on MANY HOURS of developer's talks, planning atec...
etc
ok - cu sometimes later ;)
[14:38]
...... (idle for 28mn)
***ChanServ sets mode: +o CDot [15:06]
....... (idle for 32mn)
tuorHi, (using LDAP-auth) how can I find out, in which group a user has to be, to be able to login to the wiki? [15:38]
......... (idle for 41mn)
***ChanServ sets mode: +o Lynnwood [16:19]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)