[Pidgin] #9929: Client/Server model

[Pidgin]

#9929: Client/Server model
-----------------------------------+----------------------------------------
 Reporter:  xaero                  |     Owner:  rekkanoryo
     Type:  enhancement            |    Status:  new       
Component:  unclassified           |   Version:  2.5.8     
 Keywords:  'Client/Server model'  |  
-----------------------------------+----------------------------------------
 This may have been discussed already and I missed it. I use pidgin,
 exclusively as my unified IM Client, I used it when it was GAIM as well
 and I absolutely love the client. I tend to use two or more computers at
 once, while having one that is always stable, always connected and pretty
 much always has pidgin running. There are times where I need pidgin on
 another computer. I dislike the idea of having a copy of pidgin installed
 on every computer I use. Mostly because logs get out of sync and they are
 in multiple locations and it's a pain to have to manually merge new logs
 into my archive tree.

 I looked at PortablePidgin, this was a neat idea inof itself, great to put
 on my thumb-drive (and I did, w/o logging though (a down for me, too much
 2-way data was lagging the app and the drive)).

 I then thought, why not make Pidgin Portable available over my LAN, a
 great idea, alas that failed too. The client crashed, A LOT. I went from
 no crashes, to slow/lagged access to crashes in the magnitude of 20+ in a
 very short time-span. This is where I started to *really* think and mpd
 (Music Player Daemon) popped into my head. Why not a client/server model.

 {{{
 Ex: a basic preliminary outline
 1. pidgin-server
         a. Protocol Storage/Handeling
         b. Universal Preference Storage
         c. Contact List Storage
         d. Optional Log Storage on server (with *-server)
                 a. Import old logs (feature down the road)
         e. plugin support
         f. password access

 2. pidgin-client
         a. front-end to *-server
         b. Optional Local Log Storage on computer where front-end is
 executed.
         c. theme/smiley support (maybe stored on *-server w/ 'Preference
 Storage'
         d. login-support (multiple connected clients, etc.)
 }}}

 This model, by far is not all inclusive. I fully expect it to change and
 grow as time goes by. Realistically, I can see this being shot down, but I
 hope and pray that it doesn't. I'd also like to stress that this
 idea/concept shouldn't be exclusive and replace your current product. I
 believe that if this idea were to move forward, that it should be
 developed in addition to the single-client model already in use. I am
 fully aware that not everyone has a server (weather local or remote)
 available to them and the unified client is in there best interest. But
 for the Power User, this option I think would be a great addition to
 central-storage The utilization of $HOME or windows %APPDATA% so it
 remains profile-specific on the server came to mind and I thought about
 that. If *-server can be started as a non-super user then it could easily
 be made to respect $HOME and use a non-standard port >1024 (at the admin's
 discretion to prevent port-conflicts).

 Since this is such a drastic change, maybe mark this as pidgin3?

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9929>
Pidgin <http://pidgin.im>
Pidgin