Ticket #214 (new defect)

Opened 5 years ago

Last modified 5 years ago

storage:metacontacts and GMail

Reported by: dbcm Owned by:
Priority: normal Milestone:
Component: Misc Version: version 0.8
Keywords: Cc:

Description

GMail does not support it.

<error type="cancel" code="501" > <feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/> </error>

Change History

Changed 5 years ago by melo

?/&%&/%&?$%&?""#$"# stupid service.

Let me think about this... This sucks big time...

Changed 5 years ago by dbcm

A good way is to start processing the response messages from servers. In this case, sapo msg mac should do (ask to do?) what we did in the old days.

It's ugly to go back but we need this working, my roster gets scrambled when i restart the .app.

Other thing that we need to think about it is the huge amount of data that we transmit/receive just by creating a metacontact.

Changed 5 years ago by melo

The amount of data should be solved with the move to pep, where you can have a node per meta-contact.

But not having PEP or even private storage on the server is a big problem.

I see two possibilities:

  1. going back to our previous setup: I'm also talking about "our standard" for meta-contacts in the std list;
  2. store all the information with a version attribute in all accounts.

The problem with 1. is that we loose the order attribute, and that is so nice to have. But I'm willing to sacrifice it temporally in exchange of stability.

I would like a couple of days more to see if some good idea comes out of the std list. Kevin Smith replied today that my report is not forgotten and he will reply. I hope soon.

Note: See TracTickets for help on using tickets.