[12:03:10] Trizek: You're mass-message has syntax errors... [12:03:17] == [m:Special:MyLanguage/Tech/News/2016/29|Tech News: 2016-29]] == [12:03:24] Oh, cool. [12:03:24] missing bracket [12:03:33] I can't cancel it and it has been sent to 516 pages. [12:03:35] Great. [12:03:39] :( [12:03:43] :/ [12:04:17] Sorry [12:04:38] I would have noticed it anyway. [12:05:55] And I now have an entry to add for next week issue: "due to a poor proofreading a bracket has been forgotten in last week issue's title, causing a syntax problem". [12:06:53] If I had my Windows computer with my (on vacation) I could have ran AWB and fixed the issues...:/ [12:14:36] Thanks Josve05a, I appreciate the idea. [12:22:49] searchtranslations can help [18:29:13] [[Tech]]; Hakimkh; /* [FOX]TV[] Cork City v Wolves---Live Stream Soccer Match 18 July 2016 */ new section; https://meta.wikimedia.org/w/index.php?diff=15776257&oldid=15755240&rcid=8040884 [18:29:29] [[Tech]]; MarcoAurelio; Reverted changes by [[Special:Contributions/Hakimkh|Hakimkh]] ([[User talk:Hakimkh|talk]]) to last version by Pamputt; https://meta.wikimedia.org/w/index.php?diff=15776258&oldid=15776257&rcid=8040885 [19:55:57] Anyone around to help me name a thing? [19:56:11] It's an interface for a transaction's "underbelly". [19:56:34] it has methods like onAbortDo( $callback ), onCommitDo( $callback ), etc. [19:57:02] I don't want to call it Transaction or TransactionController - these sounds like they should have begin(), commit(), and abort()... [19:57:24] So, what to call that thing? TransactionHandle? Doesn't tell me anything... [20:05:55] meh. [20:05:57] public function storeData( $data, $hints = [], TransactionUnderbelly $trx = null ); [20:06:12] Transactor! [20:06:26] Transactionatorizer! [20:07:02] TransactionCallbackHandler! [20:07:04] TransactionFollowupHandler! [20:07:47] EnterpriseTransactionHandlerWiringControllerFactorySingleton [20:07:52] But Transactionizorator sounds more impressive? [20:08:03] TransactionCallbackHandler is actually descriptive... [20:08:07] how about thinking in events? [20:08:14] TransactionEventSource. The callbacks are listeners. [20:08:27] you need Delphi to think in events :P [20:08:28] Very javaesque... [20:08:57] MaxSem: i was actually my fun days with Swing... [20:09:08] err, actually remembering [20:09:46] Anyway. TransactionCallbackHandler is the best so far, but somehow clunky. [20:09:49] "onAbortDo"? that's quite a twisted method name for an interface [20:10:02] "handleAbort"? [20:10:16] "processAbort"? [20:10:18] abortCallback? [20:11:18] How abotu a little verbing, the weird the language? [20:11:26] TransactionCallbacker? Backcaller? [20:11:38] * andre__ chuckles [20:11:49] TransactionHandler? [20:11:53] CleanerUpper? :D [20:12:03] bd808: onAbortDo( [ $this, 'killkill' ] ) [20:13:04] brion: TransactionHandler is a bit too generic i think... but yea, why not... [20:13:12] CleaerUpper, Committifier... [20:13:17] that's why we have namespaces ;0 [20:13:43] bd808: addAbortCallback( [ $this, 'killkill' ] ) is boring in comparison ;) [20:14:07] another possibility being to just take one callback, but pass an 'event' object indicating it's a rollback/abort/success [20:14:31] brought to you by the same people who invented "snaks" [20:15:21] brion: does that help with naming the interface that takes the callback? [20:15:44] DanielK_WMDE_: onTransactionComplete? meh, that sounds awful too [20:15:45] i want the storeData method to sowhere register what should happen on commit or abort. [20:15:52] TransactionCompleter..... bah [20:16:01] naming things and off by one errors, man :D [20:16:20] yea. and purging caches. story of my life. [20:16:32] TransactionFinalizer? i'm kinda digging that [20:17:43] yea... sounds nicew! but somehow i'd expect a finalizeTransaction() method there. which is not what this interface does... [20:18:08] ok then i'm back to TransactionHandler. my final offer ;) [20:18:08] TransactionBuilder? [20:18:14] hmmmmmmm [20:18:20] actually [20:18:24] that's ind of interesting [20:18:24] It is indeed a builder... though it doesn't exactly build a transaction [20:18:25] … why do you need a class for that? [20:18:44] it builds a list of things to do when the transaction (is rolled back | completed) yes? [20:19:30] MatmaRex: i have a generic data store interface. i want to store data to several different implementations, in a single transaction. each storeage operation shoudl register with the transaction, so it knows what to do on aboirt and commit. [20:19:39] brion: exactly [20:20:12] * DanielK_WMDE_ wonders if "Frank" is a good name [20:20:17] :D [20:20:23] or "Frob" [20:20:42] TransactionEscrowHolder :D [20:21:03] srsly though TransactionBuilder and TransactionManager both work for me [20:21:16] hm, in actual distributed system CS jargon, this is an undo-log. Well, at least the onAbortDo part is. [20:21:22] it's kind of 'holding the keys' of what to do to finish up a transaction [20:21:24] *nod* [20:21:38] hehe, TransactionEscrowFacilitator [20:21:47] haha you're not wrong [20:21:54] that actually makes perfect sense :D [20:21:55] (aka "salesman") [20:22:05] :) [20:22:38] TransactionLogBuilder? but "log" is a bit misleading to to casual eye [20:23:21] anyway [20:23:42] i think i'll go with TransactionBuilder. it's not great, but at least somewhat descriptive [20:23:56] thanks for the nice brainstorming session :D [20:24:24] :D [20:36:50] /part/part [20:36:53] oops