dalanik wrote:OK, that's what I thought as 1 option. But why do they have to work through P3rvTalk?
As i already mentioned my first and original reason was avoiding coding with msvc# cause i dont have that, so basicly xP3rT was set to "forward" xlobby plugin interface to my softare trough TCP/IP so i could use whatever dev env i wanted. I had none of c# programming experience beforehand so i decided not to make c# program (xP3rT) to handle multiple connections, but decided to use more familiar plain win32 c++ to code hub which should handle multiple connections (be server)... This was original reason, but i had to do so much coding with xPerT that i developed my c# skills far enough that it wouldnt really matter. However i considered that architecturaly very smart choige on severalk reasons.
Here i tried to explain few good points of architechture:
- Allthough PervTalk is originally planned to XLobby (and currently support no other front end) nothing says it cant. All u have to do is code new device for new frontend. This is also my personally insurence... if Xlobby (god forbids) dies, gets bought by microsoft and gets killed for being competitor of MCE. My whole plugin architecture can be ported to other front end simply by making one device. Instead of making whole batch of new plugins.
- Also PervTalk makes possible communication between two different front end, running on different platforms... for example lets say my car client is running Freeway, upcoming FWd can get location information from GPS, transfer it to xPerT running on my livingroom pc via PervTalk and display my cars current location on map.
- PervTalks goal is to be universal plugin infrastucture, when traditionally every pair of software requires 1 plugin to integrate them... PervTalk only reguires one device per software... let make asumption we have five software which all should communicate together... with traditional approach it takes 10 plugins to make them truly inter connected... with PervTalk it only takes 5 devices... as u add software u very soon reach combinatorial explosion with old aproach.
- I think it already came clear that PervTalk will (thanx to TCP/IP stack, which is rather universal) extend Xlobby plugin interface to any software language, any operating system, and any host (plugins can run on separate host than XLobby) I have plans to port PervHub for Linux and Symbian at somepoint.
- Based on posts here there seems to be problems to communicating between separate XLobby plugins. If these plugins are implemented in PervTalk, there will be no such problems.
- Because of those problems ive been also thinking to implement something which i call FakeLobby Device... that would fool regular xlobby plugin to believe it is working together with Xlobby, but instead it is connected to Xlobby via PervTalk... this would not only make those problems gone, but also make it possible to run current plugins on different host than Xlobby is installed.
However keep in mind that parts of infrastucture mentioned here (FakeLobby, Freeway device, linux PervHub, symbian PervHub) are just on planning board, more immeadeate future are kXd and ZPd. But since u asked my motives i had to answer with visions... lets see how it goes.
Also if u or any other developer is interested to implement PervTalk device... ill reveal PervTalk protocol, and even better yet im currently writing PervTalk library, which is currently used by kXd, its not complete yet but when it is ill be releasing it for devs to quickly implement PervTalk devices.