Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 201281" data-attributes="member: 21313">It's too bad the benefits of what I propose are not clear to the MP team.Well, Gentle is a &quot;basic&quot; ORM, not more, not less.&nbsp; It's hardly comparable to a service-oriented approach.Again, if you don't see the benefit, what can I say?&nbsp; Maybe read up on some documents about service-oriented architecture? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />A complex piece of software, and I'm sure we all agree that MP is complex enough <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />, should be broken up in manageable pieces.&nbsp; Choosing a good architecture for this is key to getting a product stable.&nbsp; Otherwise you will only get it stable by very carefully tweaking the code and never touch it again once it's stable.&nbsp; The moment you touch the code, pooooof goes the stability.So what I have here is one of those manageable pieces, the scheduling nicely split off in a well-controlled subsystem.&nbsp; I keep repeating myself, if you don't see the value of this, what can I say?Guess your reply simply means there will be no TvScheduler in TVE3 then.And please, don't make this look like I refuse to do something &quot;easy&quot; in TvScheduler, that's a distortion of the truth.&nbsp; There's nothing &quot;easy&quot; about me reading the TVE3 database, for one it's too limited in information, and secondly, since I can't know when the database changes (whereas now I do) this would add another layer of complexity, which is exactly what I was trying to avoid.&nbsp; Not to speak of totally throwing the design out of the window.</blockquote>

[QUOTE="dvdfreak, post: 201281, member: 21313"] It's too bad the benefits of what I propose are not clear to the MP team. Well, Gentle is a "basic" ORM, not more, not less. It's hardly comparable to a service-oriented approach. Again, if you don't see the benefit, what can I say? Maybe read up on some documents about service-oriented architecture? :) A complex piece of software, and I'm sure we all agree that MP is complex enough ;), should be broken up in manageable pieces. Choosing a good architecture for this is key to getting a product stable. Otherwise you will only get it stable by very carefully tweaking the code [U]and never touch it again[/U] once it's stable. The moment you touch the code, pooooof goes the stability. So what I have here is one of those manageable pieces, the scheduling nicely split off in a well-controlled subsystem. I keep repeating myself, if you don't see the value of this, what can I say? Guess your reply simply means there will be no TvScheduler in TVE3 then. And please, don't make this look like I refuse to do something "easy" in TvScheduler, that's a distortion of the truth. There's nothing "easy" about me reading the TVE3 database, for one it's too limited in information, and secondly, since I can't know when the database changes (whereas now I do) this would add another layer of complexity, which is [U]exactly[/U] what I was trying to avoid. Not to speak of totally throwing the design out of the window. [/QUOTE]

Verification