I want to bump this thread, and to reconnect it to my original point.

There is loads of replicated -- exact duplicate -- code in both xmlui, and
jspui, and is going to be further replicated in the REST API, and other
systems such as WebMVC.

Also, there is other cases where the intention is the same, but the
implementation is different. Some better, some worse.

For item metadata change.
Some have sloppy implementations: XMLUI, WebMVC (for now).
They clear all existing metadata from the item, and then add new fields of
everything that was submitted by the form.

Others have really elegant implementations: Bulk Metadata Importer
It compares the submitted metadata field with what already exists in the
item, and updates it if it has changed.

But, if there is an easy to use off-the-shelf component / business service
available to me, I'll use that instead of creating (replicating exactly) my
own. Then our performance Czar can focus on tweaking the business services.
Our reliability czar can focus on all the business services being tested.
Our New Features Czar can rest easy that the standard stuff is taken care of
for them.


I think that having Business Services available in DSpace would require that
we shift to using Services, and having the basic singleton service do
everything as normal. And then have an enhanced business service added to
gives us extra (yet very common) abilities available for each data model
object. However, this is where I (and the subject) need clarification.


Peter Dietz



On Wed, May 4, 2011 at 12:15 PM, Graham Triggs <[email protected]>wrote:

> On 4 May 2011 15:12, Mark H. Wood <[email protected]> wrote:
>
>> As usual, I want to quibble about terms.  To me, an "event" is
>> something that has already happened and I (as an event consumer) am
>> merely being notified that it has happened.  So event notices can be
>> delivered whenever we get around to it.
>>
>
> Fair enough. I would tend to talk about messages as being what's passed
> around (and can be synchronous), and events as being a special type of
> message (which is asynchronous).
>
> However, I do note that Spring has an internal synchronous notification
> system, in which it delivers ApplicationEvent. Whilst I wouldn't necessarily
> take that terminology out of choice, I wouldn't go to the lengths of
> building / integrating a different system, so I would be obliged to take on
> their terminology.
>
> G
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Dspace-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-devel
>
>
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to