|
|
08-05-2003, 09:59 PM
|
|||
|
|||
|
Very pleased with new Snapstream.net stuff!
Wow, I'm not sure if this was announced, but I never read about it. I just found out about it tonight and I LOVE IT!
Snapstream.net now will tell you what conflicts you may have and what's already scheduled! Me Likey!
__________________
Lisa W. -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* o Processor: AMD Athlon XP 2000+ 1.7GHz o Main Board: Soyo K7V Dragon Plus o Memory: Crucial PC2100 DDR 512mb (one stick) o Op Sys: Windows XP Professional (5.1, Build 2600) Service Pack 1 (2600.xpsp2.030422-1633) o Tuner Card: Hauppauge PVR 250 (1.7.21177) o Video Card: PNY GeForce3 Ti200 (5.13.0001.2188) o Sound Card: C-Media Wave Device (5.12.0001.0643) o Personal Video Station 3 (3.0.0.524) o ATI RemoteWonder o Girder 3.2 o Windows Media Player 9 (9.00.00.2980) o Video Input Method: coaxial cable o Broadcast Source: digital cable o DirectX Version: DirectX 9.0a (4.09.0000.0901) -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |_......___Ö 0_o__/__\___ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 
|
|
08-06-2003, 01:00 PM
|
|||
|
|||
|
... feature request: it's on the local machine but not remotely
Dang! I thought this was a new feature for Snapstream.net . I had never used remote programming from my SS machine. I'd always used it ... well, remotely!
Right now, to see any conflicts from a remote machine, I have to leave two browser screens open. One with SS.net page and one with the the local page for my SS machine. Back and forth viewing is required for me to see conflicts. This only works within my LAN since I'm behind a hardware firewall. So, here's my feature request: to have SnapStream.net have the same functionality as SnapStream.net on my SS machine. To be able to see conflicts... Thanks!
__________________
Lisa W. -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* o Processor: AMD Athlon XP 2000+ 1.7GHz o Main Board: Soyo K7V Dragon Plus o Memory: Crucial PC2100 DDR 512mb (one stick) o Op Sys: Windows XP Professional (5.1, Build 2600) Service Pack 1 (2600.xpsp2.030422-1633) o Tuner Card: Hauppauge PVR 250 (1.7.21177) o Video Card: PNY GeForce3 Ti200 (5.13.0001.2188) o Sound Card: C-Media Wave Device (5.12.0001.0643) o Personal Video Station 3 (3.0.0.524) o ATI RemoteWonder o Girder 3.2 o Windows Media Player 9 (9.00.00.2980) o Video Input Method: coaxial cable o Broadcast Source: digital cable o DirectX Version: DirectX 9.0a (4.09.0000.0901) -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |_......___Ö 0_o__/__\___ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
|
08-06-2003, 02:31 PM
|
|||
|
|||
|
Yes, remote conflict management is something that I've started mapping out in my head a little bit, at least on the Snapstream.Net side since I'm one of the lead devs for it.
The biggest hurdle (aside from enough hours in the day) is synching up the logic that PVS and Snapstream.Net would use in order to determine a "conflict" existed in the first place. The next biggest hurdle would be to design a data model in which the data is stored in a manner so that it is still useful and meaningful for us to provide this functionality, while still making it secure/encrypted enough that we could address privacy concerns before they're even brought up (an opt out ability would also be a requirement). And of course, all this work on the .Net side would be meaningless without matching efforts on the PVS end, so the timing of when dev starts on this has to occur in a point in time where both dev teams could work in unison... We def. want to do it though..
|
 |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Some final words before I buy this stuff! | AdmA | Home Theater PC Discussion | 5 | 09-17-2006 03:54 PM |
| Control The Other Stuff | AZman | Firefly PC Remote | 4 | 06-09-2004 01:16 PM |
| Free Stuff !!! | Treetop | SnapStream Discussion | 9 | 03-04-2004 11:25 PM |
Linear Mode
