Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The modules implementing will be the same on every call unless a new module has been enabled. We should create a cache object service:servers. This should be a serialised array structure:
array(array('#name' => 'service_name', '#path' => service_path'));
Comments
Comment #1
gddI'm marking this postponed since I don't really consider a release blocker, and from a performance standpoint I don't think it buys us much. That said if you want to write a patch and reopen within the next couple weeks that's totally cool. Just trying to wean down the open issues.
Comment #2
marcingy commentedI agree I have some thoughts on this and it makes more sense in the D7 branch. I'd like to throw out the idea of allowing for servers and services to become entities and hence become fieldable....
Comment #3
gddFor the record, marcingy and I have talked about making Services entities and fieldable but agree it should wait for a 4.x version. In the meantime, setting the original issue for consideration in 3.x.
Comment #4
marcingy commentedRenaming this issue and setting to head - the server cache seems like a micro optimisation.
If we go down the route of entities and a site is using entity cache then the caching comes for free, I'll try and think this idea through further in the new year.
Comment #5
ygerasimov commentedI am not sure but if servers and resources will be implemented via ctools plugins #855404: Use CTools' plugin system to declare resources. woudn't ctools take care about caching?
Comment #6
gddTrying to clear out the 7.3 issue queue, will move these to 7.4 when it opens
Comment #7
marcingy commentedClosing again because there is no real benefit to this as I can after using the module in the real world.