More standard practices
Hello,
This is a great application in both commercial as well as educational standpoint. Here are some of my wishlist:
1. Ability to change the project on a particular task.
2. Ability to refresh instead of restarting or offline/online
3. Ability to delete the tasks by the admin.
4. Adding one more userlevel called Project manager, who can manage the tasks under each project
5. Tasks and Subtasks
There are many more. But I think it is a good start.
Thanks
Naga
How about having the client window let you know if a task has been added. I'm thinking something similar to what Outlook does when working with Exchange and a new mail message is delivered; you get an instant notification of the delivery (none of this waiting ten seconds or so to poll the server, the server sends a notification immediately).
I don't think that the primary goal is to provide a useful application (although TaskVision succeeds at this anyway) but rather to provide an example of a FINISHED application created in .NET
The problem is that sample code is usually only complete to the extent that it needs to be in order to make the point-- the polish nessesary for a "real" app isn't there. The unintended result of this is that developers often don't know how to build a "real" application because they have never seen one.
TaskVision is a GREAT idea-- I'm really glad MS has created an end-to-end solution like this. This is what Terrarium should have been: allowing the development community to see the inside of a real-world, finished application as a way of demonstrating best practices.
MartinJ, wouldn't that involve a socket server or something? not that i think that's a bad idea...just asking
btw, recognize me from GDN (I'm "mybutt" on there)? :p Good to see you over here! :)
Actually I think if enough people were interested than, something could be started like "ASP.NET Forums Source Code Share" where people show their code on how they modified the sample code.
I guess we'll have to see if some people perform mods to the code, might not be popular to do as re-using the forum code is.
Not a bad idea though... That could be accomplished using a .NET Remoting object. A server activated object could callback to clients. Web Services were chosen because of their friendliness :-) They're a lot easier to consume by client applications on different platforms and they're very firewall friendly.
I've put a little thought into this. It uses an extra web service for registering and unregistering interested parties. A windows service would do the actual sending of notifications to keep the web services from either locking or dying because they are just asp.net applications.
The notifications would be sent out using UDP packets so that there are no waits if the client is no longer listening. If a client receives a notification, it sends a reply TCP packet to the windows service. The UDP packets would get sent out every so often (something like 30 seconds to make sure that a reply could've been sent) until a reply came in. The windows service would unregister any client that doesn't send a reply back within a few minutes.
Of course, there would have to be some kind of unique number assigned to the notification so that both client and server know which notification they are talking about.
I looked into using the Alerts API. But, that appears more geared to notifying people, not applications.
Great ideas. In a couple of weeks, we'll be posting an update that has some cool security features built in and support for dealing with proxy servers. Because there are so many other sample apps we want to write, we won't have the resouces to add too many NEW features to TaskVision beyond this.
That said, have you seen GotDotNet workspaces? http://www.gotdotnet.com/community/workspaces/
I say we take this over there and create a community project around extending it...
Anyone care to "own" the project and get it started?
for educational purposes I wish:
1. more documentation about design considerations, more comment in the sourcecode
2. show how to implement UNDO menu items
3. include deployment project
4. deliver an ASP.NET Web client with an user interface as close as possible to the windows client
5. publish the amount of development time that went into the example, by layer ...
please more end-end examples like this!
thanks
herbert
I'm a bit too busy to own it myself, but that sounds like an excellent idea to me :)
>Ability to refresh instead of restarting or offline/online
I have been working on application that is loosely based on the TaskVision architecture. My solution to the refresh issue was to implement a serial number. Each time an update is posted to the Web Service the serial number is incremented. The clients check the serial number on a regular basis and retrieve changes as needed.
Brandon Johnson
<quote>
jrj102 wrote:This is what Terrarium should have been: allowing the development community to see the inside of a real-world, finished application as a way of demonstrating best practices.
</quote>
Isn't that the truth...I wrote that to the GotDotNet feedback when 1.1 came out but got no reply. I know it was intended as a training bed for web services but think how much more we could have learned from the source of the client and the server.
I would opt for remoting w/ both TCP and HTTP channels registered.
Any idea of the release date for the update?
Thanks
Probably about 2-ish weeks, give or take a few days... ;)
