|
I read your name as "Pay-Pal".
OK,. what country just started work for the day ? The ASP.NET forum is flooded with retarded questions. -Christian Graus
Best wishes to Rexx[^]
|
|
|
|
|
i try to make a crawler that crawls the web page
and retrieves the stock information from google (i.e)
in a google page contain stock infrmn,but i want
to fetch & display particular field infrmn.
but can't do it. so pl help me.
very urgent.
|
|
|
|
|
Have you and the guy below been busy doing something unsavoury so that you've missed your homework deadline?
|
|
|
|
|
Figure it out yourself.
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
Very easy... just by coding..
OK,. what country just started work for the day ? The ASP.NET forum is flooded with retarded questions. -Christian Graus
Best wishes to Rexx[^]
|
|
|
|
|
i try to make a crawler to fetch the webpage in php.
in a webpage,i want to display a particular field.
very urgent.help me.
sg
|
|
|
|
|
Figure it out yourself. This is a Microsoft/.NET/Visual Studio centric cite. You probably won't find much help with PHP here.
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
My xml file stores some data about different types of shapes and I want to load only those shapes which are being display, if a Next button is clicked it displays a shape if clicked again displays another shape. A shapecontrol may have picturebox control so how can I separate the shape control from its data. I know that i have to look into MVC pattern and have read about it but can't really figure out how to put together to get the result i want.
Basially i want to build like Ms power points. If power point we can add differnt kidns of objects and can view there raw data like height,width. Basially, i think controls are separted from data. That's what i want to
|
|
|
|
|
Obviously I can't post a complete solution, I've worked on the equivalent of MS PowerPoint and it was years of work. In general I would say to separate controls from data start by forgetting about the controls. Just think of the data, how to store it, retrieve it, access it and structure it. Then think about the controls as something you do with the data. When you do that you'll suddenly find you need data you didn't think of before. Add that to your original list and start over with getting your data structures right. Only when you switch to thinking about the controls and find all the data you need is readily available from your containers in a fast and safe manner then start on the controls for real.
The trick, if there is one, to a GUI heavy application is to do as little as possible in the GUI code and as much as possible in the data layer.
Nothing is exactly what it seems but everything with seems can be unpicked.
|
|
|
|
|
Hi everyone,
Can someone explain whether VS2008 will work with SQL Server 2005? I wasn't sure if VS2008 only works with SQL Server 2008.
Also, does anyone know if SQL Server 2008 Express offer Reporting Services? My client does not want to spend money on a SQL Server license, so I'd like to install SQL Server 08 express...but only if Reporting Services is part of it.
Thanks everyone, happy new yr
John
|
|
|
|
|
camby75 wrote: VS2008 will work with SQL Server 2005
Yes. It does.
Any particular reason why the jump to SQL Server 2008? If the client is okay with using 2005 and doesn't want to pay for 2008, don't do the jump up to 2008, then.
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
|
Even though i understand Architecture. still I can't explain clearly to my subordinates. I referred numerous web pages but they give a fuzzy explanation. Can any one help me ?
kannabiran
|
|
|
|
|
Kannan.P wrote: I referred numerous web pages but they give a fuzzy explanation
Because of it is a fuzzy concept .
Well, some exposure to OOP would help, anyway have a look at http://en.wikipedia.org/wiki/Software_architecture[^]
BTW what are your subordinates roles?
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
thanks for reply
my subordinates are programmer trainees. They just do code with my guidance.
kannabiran
|
|
|
|
|
If they haven't OOP exposure, maybe the time to fill the gap.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
Ah.... software architecture. Very good question. There really isn't a clear definition, although there is a informal standard (yeah, these 2 words don't go well together).
Software architecture can be defined as a design and blueprint of how the software components will work with each other, which objects are part of the software, how objects will interact with each other, and so on.
There can be a high-level architecture which may include:
Tier layers such as Database, application and UI.
And there can be a low-level architecture which may include:
Objects (classes) which are part of the software solution.
Most good software architects design the entity relationships and classes after designing a good and clear functional design.
A process in which I follow:
1) Design clear functional specifications which include detailed use cases of how each requirement will be implemented. (actually this is more of a job for a good technical analyst)
2) Design the component, state, process and class diagrams as detailed as possible.
Basically the end result should be a clear blueprint of how the software should be developed. Therefore a developer would just do the "implementation" and the design to have already been done by the software architect, hence the developer becomes a "robot" following the instructions of the architect.
I hope above helps.
Arsen
|
|
|
|
|
I'm creating a Windows service that will be responsible for hosting and general management of additional modules with a common interface. Typically, these modules will be responsible for invoking a Workflow Foundation workflow, but that will not be a design requirement -- the only requirement is that the module adheres to the interface. I will not necessarily have control of what goes on in each module. Therefore, reliability of the remaining modules is a concern.
Currently, I'm considering a scenario where the Windows service manages the creation and lifetime of one or more separate host processes (EXE) where each host process is simply a shell to run a host module. Remoting would be used for interprocess communication such as start, stop, health, common services (provided from the service), et al.
The good thing about this design is that I can easily manage the state of the processes and spawn new ones as needed -- OOM situations, poorly behaving workflows, etc.
My first concern with this design is security. Specifically, I would want the host processes to run within the same security context as the service that created it. I will test this at some point soon, but I figured someone would probably know this offhand.
My second concern with the design is the Workflow Foundation resources. Each host process would get its own instance of the Workflow Runtime and there could possibly be several host processes running. Would this create as unnecessary burden on the computer as I think it would -- especially considering I would take advantage of some of the WF services such as the tracking and persistence services.
And finally if this architecture sounds overally burdensome, do you have any other recommendations?
|
|
|
|
|
tgrt wrote: that will be responsible for hosting and general management of additional modules with a common interface.
That sound a lot like what the Com+ Appilcation Server does. Is there some reason you are not using it?
|
|
|
|
|
This will be a 100% managed application using C#. I'm not familiar with the capabilities of the COM+ application server. But, I can say that the service will be providing more than trivial capabilities to each of the modules.
|
|
|
|
|
tgrt wrote: This will be a 100% managed application using C#
Even more reason to look at COM+, the BCL has classes for create Com+ Serviced components. Check it out[^].
|
|
|
|
|
Thank you for the article. It seems to be focused more on the transaction side. However, I will look into the COM+ serviced components further to make sure they'll meet all my requirements. The modules that will be managed by the service will work independently of one another and additionally the workflows they run will work independently of one another.
The ultimate question of reliability will come when I determine what happens when an OOM exception occurs in the COM+ serviced component. The last thing that can happen is that the service is corrupted in any way shape or form.
|
|
|
|
|
tgrt wrote: when an OOM exception occurs
an Out Of Memory exception?
tgrt wrote: The last thing that can happen is that the service is corrupted in any way shape or form.
Again without knowing more about your requirements I'm just guessing. This is because you need to execute modules you don't trust? If the supplied modules don't handle their own errors what are you going to do to ensure against corruption? So you handle the exception and then what?
|
|
|
|
|
You're correct, when I say OOM, I mean out of memory condition which might be an out of memory exception or stack overflow exception, etc. Anything that fits within a broad category of non-application based exceptions.
I'm trying to provide enough information without laying out all of the requirements which is obviously not possible within this medium.
The executed modules will trusted in the context of security, but not within the context of stability. For example, I'll provide the controlling service (through whatever that turns out to be) and several executing module. The user, being a system administrator or developer type, will choose which ones they need and create workflows that execute based on criteria dependent on each executing module. The user can also extend the solution in such a way as creating their own executing modules based on a common interface.
What I don't want is for a executing module to fail and bring down other executing module or even worse the service itself. The service will monitor the health of the executing modules and if there is a failure it will cleanup anything that is necessary and start a brand new shiny executing module to pick up where the old one left off.
|
|
|
|
|
tgrt wrote: What I don't want is for a executing module to fail and bring down other executing module or even worse the service itself. The service will monitor the health of the executing modules and if there is a failure it will cleanup anything that is necessary and start a brand new shiny executing module to pick up where the old one left off.
Yes the Com+ Application Server does all of that
|
|
|
|