网站帐户的应用“信息中心” [英] Application 'dashboard' for website accounts

问题描述

Hello社区，我是一名基本的c＃程序员。我经常面临定期检查帐户的任务。



哪里是开始构建程序的好地方我可以'插上在'到我的帐户;

paypal，

ebay，

gmail，

adsense，

analytics，
或我想跟踪活动的任何通用帐户;

并实施一个桌面甚至托盘图标警报系统，它会通知我任何消息，paypal交易，电子邮件或任何活动变化等..



可以做客户端吗？我从哪里开始，还有其他人做过吗？



感谢您的反馈 -

Cody

Hello community, I am a basic c# programmer. I am constantly faced with the task of checking accounts on a very regular time interval.

Where would be a good place to start to build a program that I could 'plug in' to my accounts;
paypal,
ebay,
gmail,
adsense,
analytics,
or any generic account that I want to track activity from;
and implement a 'desktop' or even tray icon alert system that would notify me of any messages, paypal transactions, emails, or any activity changes etc..

Is that possible to do client-side? Where would I even start with this, has anybody else done it?

Thanks for your feedbacks -
Cody

推荐答案

一个好的起点是查找要管理的每个服务的任何可用公共API。然后你创建与API通信的小测试程序，在每个工作之后，开始将它们拼接在一起。



有关于如何制作一个的教程托盘应用程序，只需搜索谷歌的C＃托盘应用程序。



你也可以看一下插件式应用程序，我会推荐Mono.Addins，但是如果你真的很有抱负，那么你可以尝试使用MEF。

A good place to start would be to look up any available public API's for each service you want to manage. Then you create small test programs that communicate with the API's, after you have each one working, start stitching them together.

There are tutorials out there on how to make a tray application, just search google for something like "C# Tray Application".

You can also look at doing plug-in type applications, I would recommend Mono.Addins, but if you are really ambitious then you can try using MEF.

这是个不错的主意......至少，我可以看到它有一些相当大的价值，但是......不幸的是，在一般情况下，更不幸的是，在大多数情况下，这是不可能的在客户端有通知。为什么？简而言之：支持客户端 - 服务器模型，缺乏服务器推送，缺乏发布者 - 订阅者模型。



对于某些背景，请参阅：

http://en.wikipedia.org/wiki/Client-server_model [ ^ ]，

http://en.wikipedia.org/wiki/Polling_%28computer_science%29 [ ^ ]，

http://en.wikipedia.org/wiki/Pull_technology [ ^ ]，

http://en.wikipedia.org/wiki/Server_push [ ^ ]，

http://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern [ ^ ]。



嗯，是的，在客户端你仍然可以求助于所有服务的客户轮询，但这种方法很受欢迎，是如此恶心，我不想讨论它。我认为这种方法很清楚，特别是如果你阅读上面引用的文章。



一些想法：



不久前，甚至客户端 - 服务器方法，特别是在数据库管理领域，被许多天真的用户和开发人员（如果不是他们中的大多数人）认为是革命性的和进步的。与之前网络和基于文件系统的产品的噩梦形成对比的效果已经发挥了作用。尽管客户端 - 服务器/拉动技术的严苛局限对那些真正能够思考的人来说非常明显，而且更全面的技术绝对可行，但并不是很多人听到了原因的声音。而现在，这样认为服务器推送不足的原因几乎100％显而易见，因为它甚至会伤害非常基本的需求，例如合理设计的聊天应用程序，人们回到服务器推送或发布者订阅者，感觉更多的阻力由于由惯性思维（甚至防火墙等）创造的标准和技术。这种解决方法的任何一个例子？这是一个非常引人注目的问题：

http://en.wikipedia.org/wiki/SignalR [ ^ ]，

< a href =http://www.asp.net/signalr> http://www.asp.net/signalr [ ^ ]。

-SA

Would be a pretty good idea… At least, I can see some considerable value in it, but… Unfortunately, in general case, and, even more unfortunately, in most cases, this is impossible to have notifications on the client side. Why? In a few words: domination of client-server model, lack of server push, lack of publisher-subscriber model.

For some background, please see:
http://en.wikipedia.org/wiki/Client-server_model[^],
http://en.wikipedia.org/wiki/Polling_%28computer_science%29[^],
http://en.wikipedia.org/wiki/Pull_technology[^],
http://en.wikipedia.org/wiki/Server_push[^],
http://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern[^].

Well, yes, on client side you still could resort to client polling of all the services, but this approach, being popular enough, is so disgusting that I don't want to discuss it. I think this approach is clear enough, especially if you read the articles referenced above.

Some thoughts:

A while ago, even the client-server approach, especially in database management field, was perceived as revolutionary and progressive by many naive users and developers, if not the most of them. The effect of the contrast with the nightmare of before-networks and file system based products has played its role. Even though the draconian limitations of client-server/pull technology was quite apparent to those who could really think, as well as the absolute feasibility of more comprehensive technologies, not many listened to the voice of the reason. And now, such think where the lack of server push because nearly 100% apparent, because it hurts even the very basic needs, such as reasonably designed chat application, people come back to server push or publisher-subscriber, feeling much more resistance due to standards and technologies created by inertia of thinking (and even such things as firewalls). Any example of such workaround? This is a pretty striking one:
http://en.wikipedia.org/wiki/SignalR[^],
http://www.asp.net/signalr[^].

—SA

探索Web套接字及其实现方式。

这可以为您提供一个可以实现发布 - 订阅机制的平台。

Explore web sockets and way to implement them.
This could provide you with a platform where you can implement a publish - subscribe mechanism.

这篇关于网站帐户的应用“信息中心”的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！