CoreCommunity ExtensionsIncubatorDistributionsTYPO3 4.5 ProjectsTYPO3 4.7 ProjectsTYPO3 6.0 ProjectsTYPO3 6.1 ProjectsTYPO3 6.2 Projects (+)

Major Feature #2857

Define base service structure for client

Added by Francois Suter over 4 years ago. Updated 11 months ago.

Status:Closed Start date:2009-03-16
Priority:Must have Due date:
Assignee:Francois Suter % Done:

90%

Category:Basic Bricks Spent time: -
Target version:-
Votes: 0

Description

In the current, example implementation each information-gathering service (base, extensions) is implemented as a separated remote service. This means that a client will have to be queried several times to get all the information. It would be more efficient to be able to make a single call to a client and get all the information back. OTOH the flexibility to get only a given set of information is also nice.

We can achieve this flexibility by having a single remote service which accepts the name of an information-gathering service as an argument. If none is given, all services are called. Information-gathering services thus become TYPO3 services (with subtypes for each set of information) and not remote services.

To get the data from all information-gathering services, we need a new pattern to get a service object for each possible subtype.

Associated revisions

Revision 21551
Added by Niels Pardon about 4 years ago

[Bug 2857] Feature: Provide a RealURL configuration

Revision 21552
Added by Niels Pardon about 4 years ago

[Bug 2857] updating manual

History

Updated by Xavier Perseguers over 4 years ago

Having a single remote service which accepts the name of an information-gathering service would be nice but let do it a bit more generic and allow a list of services to be given as argument.

If none is given, all services are called: fine!

Updated by Francois Suter over 4 years ago

Having a single remote service which accepts the name of an information-gathering service would be nice but let do it a bit more generic and allow a list of services to be given as argument.

Of course, makes absolute sense! Well spotted.

Updated by Francois Suter about 4 years ago

  • Status changed from New to Accepted
  • Assignee set to Francois Suter
  • % Done changed from 0 to 90

Base services are in place as of revision 18441

Updated by Francois Suter about 4 years ago

Francois Suter wrote:

Base services are in place as of revision 18441

Note: Xavier's suggestion not taken into account yet.

Updated by Francois Suter 11 months ago

  • Status changed from Accepted to Closed

I'm closing all the related issues, since this is not developer anymore. Caretaker should be referred too instead: http://forge.typo3.org/projects/show/extension-caretaker

Also available in: Atom PDF