Ticket #2467 (reopened enhancement)

Opened 3 years ago

Last modified 2 years ago

Add a documented mechanism for `MessageQueue.queueMessage` to send messages to application stores

Reported by: pjd Assigned to: glyph
Priority: normal Milestone:
Component: Mantissa Severity: normal
Keywords: Cc:
Estimated Completion (YYYY/MM/DD): Branch:
Author:

Description (Last modified by glyph)

As implemented in #2191, messages can only be queued to user stores. Thanks to the fact that app stores have loginmethods created to point at them, you could probably make this work to talk to an app store, but that would largely be an accident if it worked. There should be a specific, documented, tested way to get a value for the 'target' Identifier that will reliably send a message to a particular application store.

As part of this ticket, we should also decide on the semantics of application stores as they may be represented in a cluster. Are they replicated? What is the read/write master relationship? I have some ideas here and I should write them all down.

Change History

02/11/08 17:31:14 changed by oubiwann

  • milestone set to Mantissa Community Release.

02/17/08 20:23:42 changed by mithrandi

See also #2270.

02/26/08 03:20:47 changed by glyph

  • status changed from new to assigned.

07/08/08 01:35:01 changed by glyph

  • status changed from assigned to closed.
  • resolution set to invalid.
  • milestone deleted.

Description has gone not-filled-in for long enough that I've completely forgotten what this ticket was about. Anyone who can remember can reopen. (Let's stop doing this.)

08/12/08 22:54:02 changed by glyph

  • status changed from closed to reopened.
  • resolution deleted.
  • description changed.
  • summary changed from Application store access interface to Add a documented mechanism for `MessageQueue.queueMessage` to send messages to application stores.

Okay now I remember what this ticket was about.

jethro@divmod.org