[ Outline ] · Standard · Linear+ Webserver with Ajax and XML

[Darklord]

Ok, as promissed, im reporting on what i have done.

Here is the code for the prototype i have been working on, to test the concept and check some of the changes needed to implement it.

The code isnt meant to be added, just for checking and commenting; it was done against the code on SourceForge cvs (public, of course).

Following are some notes of implementation, covering what i have found out, done and thought about.

[Aw3]

Yep, and that is also one of the strong points of the ajax way, since it doesnt reload the entire page, just the changing bits.

How does the server know what to resend? Do you keep the copy of everything transferred to a client?

It doesnt.
Its up to the client to decide what and when to ask, and what to do with it once it arrives. Its a pull strategy instead of a push.

You were mentioning all the time that only changed fields should be retransmitted. How can the client know which fields changed?

Im suprised noone has commented on this:

As the webserver as it was couldnt serve XML, i made the necessary changes (an ugly and imcomplete hack, the webserver needs serious refactoring); when done, it hit me with the new possibilities of this new interface:

- possibility of any XML aware program being able to monitor and control emulePlus easily; this includes IM programs, IRC programs, scripts, whatever...

I think this is a very useful feature. To give a better ideia, i implemented another prototype, this time a Yahoo Widget, that can monitor eMulePlus through the XML interface.

Usually it works in the following way -- the more "useful" features you have, the less security you provide...

[Darklord]

You were mentioning all the time that only changed fields should be retransmitted. How can the client know which fields changed?

Where did i said that?

What i did say was, what is transmited is the data, what CAN change.

Take a look at the requests i mentioned, call them on the browser. That is what its transmitted.

The structure of the document wont change (much), at least while you are in a page, so there is no need to send it every time.

Usually it works in the following way -- the more "useful" features you have, the less security you provide...

Perhaps.

Should we not implement anything else then, with fear of that? Or should we try to think ways to avoid most problems and attack vectors, while implementing new features?

Why even use a tool thats connected to such a dangerous thing as the internet? Better to just unplug that cable

EDIT: as for this feature, it just uses the same mechanism of the webserver. If there is a an attack vector in it, theres probably also in the already existing webserver.

Unless you mean the other programs, and that is not our concern.

This post has been edited by Darklord: Jun 9 2006, 00:44