@eholmila not outside of switching the API from using safe Midgard GUIDs to unsafe integers
bergie
commented on
posted to #Qaiku-api
Helsinki
22.07.2010
(en)
If Qaiku API would use integers as id's:
It would be more twitter compatible
It would be possible to get numbers of different clients to work with Qaiku -- For example Tweetdeck
I understand that current implementation is beautiful. I believe it helps to support for example Organisaatio Qaiku (you have several instances of system). Still, could you think them as a separate services and have unique integer ID's for each "domain"? Would it be possible to have mapper between those ID's and still get enough performance out?
Ile
commented on
posted to #Qaiku-api22.07.2010
(en)
@Ile we do have integers for each message, so this would be an one-liner fix in API. The question is, do we want to do it. I'll leave the decision to @tepheikk and @eholmila :-)
bergie
commented on
posted to #Qaiku-api
Helsinki
22.07.2010
(en)
The GUIDs can be represented as (very large) integers in addition/instead of the current hex-encoding.
Of course the clients will probably choke and crash if you give them numbers in the 2^144 -range (hell, many did when twitter itself overran the 32bit unsigned int and that's many many magnitudes smaller....)
Edit: I'm also fairly sure PHP cannot handle so large numbers either so in practice this is a moot point...
